Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(docs): Added details about creating service-account.yml file #256

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

fix(docs): Added details about creating service-account.yml file #256

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98fb654
Added escape for special characters in link. Also modified link text …
Jul 13, 2022
e7e9e9e
fix(docs): link to creating a service account
tsonny Oct 17, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 7 additions & 3 deletions content/en/docs/setup/install/providers/kubernetes-v2/_index.md
View file
Open in desktop
Expand Up @@ -39,16 +39,20 @@ The Kubernetes provider has two requirements:

### Optional: Create a Kubernetes Service Account

If you want, you can associate Spinnaker with a [Kubernetes Service
You can associate Spinnaker with a [Kubernetes Service
Account](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/),
even when managing multiple Kubernetes clusters. This can be useful if you need
to grant Spinnaker certain roles in the cluster later on, or you typically
depend on an authentication mechanism that doesn't work in all environments.

Given that you want to create a Service Account in existing context `$CONTEXT`,
the following commands will create `spinnaker-service-account`, and add its
The following example assumes you want to create a Service Account in an existing context `$CONTEXT`.
In this example, the commands create the `spinnaker-service-account`, and add its
token under a new user called `${CONTEXT}-token-user` in context `$CONTEXT`.

{{% alert color="info" title="Tip" %}}For more information about creating a Service Account, see [Creating service accounts](https://spinnaker.io/docs/setup/other_config/security/authorization/service-accounts/#creating-service-accounts).{{% /alert %}}

```bash

```bash
CONTEXT=$(kubectl config current-context)

Expand Down
4 changes: 2 additions & 2 deletions content/en/docs/setup/install/providers/kubernetes-v2/k8s-provider.md
View file
Open in desktop
Expand Up @@ -6,7 +6,7 @@ description: >
---

Spinnaker's Kubernetes provider fully supports Kubernetes-native, manifest-based deployments and is the recommended provider for deploying to Kubernetes with Spinnaker.
[Spinnaker's legacy Kubernetes provider](https://www.spinnaker.io/setup/install/providers/kubernetes/)
[Spinnaker\'s legacy Kubernetes provider](https://www.spinnaker.io/setup/install/providers/kubernetes/)
is [scheduled for removal](https://github.com/spinnaker/governance/blob/master/rfc/eol_kubernetes_v1.md) in Spinnaker 1.21.

## Accounts
Expand Down Expand Up @@ -96,7 +96,7 @@ you must specify that namespace when you add the account to Spinnaker.
If you don't specify any namespaces, then Spinnaker will attempt to list all namespaces,
which requires a cluster-wide role. Without a cluster-wide role configured
and specified namespaces, you will see deployment
[timeouts in the "Wait for Manifest to Stabilize" task](https://github.com/spinnaker/spinnaker/issues/3666#issuecomment-485001361).
timeouts in the [\"Wait for Manifest to Stabilize\" task](https://github.com/spinnaker/spinnaker/issues/3666#issuecomment-485001361).

```yaml
apiVersion: rbac.authorization.k8s.io/v1
Expand Down