diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 93a487580..c8df6d6e9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -4,7 +4,7 @@ We’d love to accept your patches and contributions to this project. Please rev # Communication -We prefer communicating asynchronously through GitHub issues and the [k14s Slack channel](https://kubernetes.slack.com/archives/CH8KCCKA5). In order to be inclusive to the community, if a conversation related to an issue happens outside of these channels, we appreciate summarizing the conversation's context and adding it to an issue. +We prefer communicating asynchronously through GitHub issues and the [#carvel Slack channel](https://kubernetes.slack.com/archives/CH8KCCKA5). In order to be inclusive to the community, if a conversation related to an issue happens outside of these channels, we appreciate summarizing the conversation's context and adding it to an issue. # Propose a Change diff --git a/README.md b/README.md index c5dd9ed4b..cef99cdae 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # kapp - Website: https://get-kapp.io -- Slack: [#k14s in Kubernetes slack](https://slack.kubernetes.io) +- Slack: [#carvel in Kubernetes slack](https://slack.kubernetes.io) - [Docs](docs/README.md) with topics about diff, apply, gitops, config, _blog posts and talks_ etc. - Install: grab prebuilt binaries from the [Releases page](https://github.com/k14s/kapp/releases) or [Homebrew k14s tap](https://github.com/k14s/homebrew-tap). diff --git a/docs/rbac.md b/docs/rbac.md index e44be5c04..89de9901c 100644 --- a/docs/rbac.md +++ b/docs/rbac.md @@ -8,7 +8,7 @@ Following setup is currently expected by kapp (v0.10.0+): - [optional] kapp requires one `ClusterRole` rule: listing of namespaces. This requirement is necessary for kapp to find all namespaces so that it can search in each namespace resources that belong to a particular app (via a label). As of v0.11.0+, kapp will fallback to only [state namespace](state-namespace.md) if it is forbidden to list all namespaces. - otherwise, kapp does _not_ require permissions to resource types that are not used in deployed configuration. In other words, if you are not deploying `Job` resource then kapp does not need any permissions for `Job`. Note that some resources are "cluster" created (e.g. `Pods` are created by k8s deployment controller when `Deployment` resource is created) hence users may not see all app associated resources in `kapp inspect` command if they are restricted (this could be advantageous and disadvantegeous in different setups). -Please reach out to us in #k14s channel in k8s slack (linked in [README.md](../README.md)) if current kapp permissions model isn't compatible with your use cases. We are eager to learn about your setup and potentially improve kapp. +Please reach out to us in #carvel channel in k8s slack (linked in [README.md](../README.md)) if current kapp permissions model isn't compatible with your use cases. We are eager to learn about your setup and potentially improve kapp. Example of `Namespace` listing permission needed by kapp: diff --git a/pkg/kapp/website/templates/index.html b/pkg/kapp/website/templates/index.html index dcd3a669a..0d82cd943 100644 --- a/pkg/kapp/website/templates/index.html +++ b/pkg/kapp/website/templates/index.html @@ -18,7 +18,7 @@

@@ -495,7 +495,7 @@

Carvel Team