Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.scaleway.com/en/docs/kubernetes/how-to/connect-cluster-kubectl/ below:

How to connect to a Kubernetes Kapsule cluster with kubectl

1. Home
2. Kubernetes
3. How to
4. How to connect … er with kubectl

Once your cluster is created, you can install a kubeconfig file using Scaleway's command-line tool on your local machine to manage your Kubernetes cluster.

You can use this with kubectl, the Kubernetes command-line tool, allowing you to run commands against your Kubernetes cluster. This enables you to deploy applications, inspect and manage cluster resources, and view logs directly from your local machine.

To complete the actions presented below, you must have:

• A Scaleway account logged into the console.
• Owner status or IAM permissions to perform actions in the intended Organization.
• Created a Kubernetes Kapsule cluster.
• kubectl installed locally.
• The Scaleway CLI installed locally.

If your Organization uses IAM to control access, ensure that you or your group/application has the following permission sets assigned at the Project scope:

• KubernetesFullAccess (or KubernetesReadOnly, depending on your needs): Grants you the ability to manage (or list/read) Kubernetes clusters, nodes, and related actions in your Scaleway Project.

If you have not yet configured IAM on your account, you can generate a kubeconfig file with IAM and the required permission sets from the Scaleway console after creating a cluster.

You can use the Scaleway CLI to automatically retrieve (and merge) your kubeconfig file, then interact with your Kubernetes cluster.

If you have not set up the Scaleway CLI yet:

1. Follow our installation guide for platform-specific instructions using Homebrew, Chocolatey, or manual methods.
2. Run the following command and follow the prompts to set up your CLI with your Scaleway API keys: You will need your API Key (access key and secret key).

1. Run the following command to install the kubeconfig file for your cluster:

   scw k8s kubeconfig install <cluster-id>

   This command will:

   • Download the kubeconfig for the specified cluster.
   • Merge it into your existing kubeconfig file (default location: ~/.kube/config).

2. Verify the installation:

   A list of nodes from your Kapsule cluster should appear.

Refer to our complete Documentation for scw k8s to learn more about all available commands to manage your Kubernetes cluster using scw.

When a user loses access rights (e.g., departs from the Organization), the Kubernetes administrator must take steps to revoke their access to the cluster. This is typically done by modifying IAM settings, such as adjusting policies or deleting the user’s credentials.

To revoke a user's access to the cluster, ensure that any API keys associated with the user are no longer granted permission. Here are the steps you can take:

• Locate the API key associated with the user.
• Remove the key to immediately revoke access.

• Adjust the IAM policy linked to the API key to limit or remove its permissions.

• Transfer the principal (application or user) to a group with reduced permissions that does not allow cluster access.

• Permanently remove the user or application from the IAM system to ensure no further access is possible.

To permanently revoke kubeconfig access via IAM:

• Delete the API Key: This will ensure that the user's kubeconfig file becomes invalid immediately.
• Delete the Principal: Removing the user or application guarantees that no further access can be gained, even if residual configurations exist.

• Be cautious when modifying IAM policies to avoid unintended access issues for other users or services.
• Regularly audit IAM settings and API keys to ensure compliance with organizational security policies.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4