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.

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

Remove vintage OIDC tutorial #2444

Merged
merged 2 commits into from
Jan 10, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ We utilize Kubernetes-native RBAC to control access to resources in the platform

### Authentication: Workload Cluster

For the workload cluster - where you run your applications - we don't enforce any specific OpenID Connect (OIDC) tool to enable single sign-on (SSO). However, if you wish to implement SSO for accessing your workload cluster, we provide a detailed guide on how to configure Dex for this purpose, you can follow our comprehensive guide: [Configure OIDC using Dex to access your clusters]({{< relref "/vintage/advanced/access-management/configure-dex-in-your-cluster/" >}}).
For the workload cluster - where you run your applications - we don't enforce any specific OpenID Connect (OIDC) tool to enable single sign-on (SSO). However, if you wish to implement SSO for accessing your workload cluster, we provide a detailed guide on how to configure Dex for this purpose, you can follow our comprehensive guide: [Configure OIDC using Dex to access your clusters]({{< relref "/tutorials/access-management/configure-dex-in-your-cluster/" >}}).

### Authorization: Workload Cluster

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ menu:
user_questions:
- How can I configure OIDC in my cluster?
- How can I add a new OIDC connector?
last_review_date: 2024-11-29
last_review_date: 2025-01-09
owner:
- https://github.com/orgs/giantswarm/teams/team-bigmac
---
Expand All @@ -37,57 +37,6 @@ The `Kubernetes` API allows users to authenticate using the `OIDC` protocol, mak
You need to set values for the OpenID Connect (OIDC) issuer address and client ID. You can define those values in the cluster custom resource. These values will then be set as flags on the `Kubernetes` API server (specifically, `--oidc-issuer-url` and `--oidc-client-id`).

{{< tabs >}}
{{< tab title="Azure">}}

```yaml
apiVersion: cluster.x-k8s.io/v1alpha3
kind: Cluster
metadata:
annotations:
oidc.giantswarm.io/client-id: dex-k8s-authenticator
oidc.giantswarm.io/issuer-url: https://dex.CLUSTER_NAME.BASE_DOMAIN
oidc.giantswarm.io/group-claim: groups
oidc.giantswarm.io/username-claim: email
...
```

{{< /tab >}}
{{< tab title="AWS">}}

```yaml
apiVersion: infrastructure.giantswarm.io/v1alpha2
kind: AWSCluster
spec:
cluster:
...
oidc:
claims:
groups: groups
username: email
clientID: dex-k8s-authenticator
issuerURL: https://dex.CLUSTER_NAME.BASE_DOMAIN
```

{{< /tab >}}
{{< tab title="OpenStack">}}

```yaml
apiVersion: controlplane.cluster.x-k8s.io/v1beta1
kind: KubeadmControlPlaneTemplate
spec:
template:
spec:
kubeadmConfigSpec:
clusterConfiguration:
apiServer:
extraArgs:
oidc-issuer-url: https://dex.CLUSTER_NAME.BASE_DOMAIN
oidc-client-id: dex-k8s-authenticator
oidc-username-claim: email
oidc-groups-claim: groups
```

{{< /tab >}}
{{< tab title="Cluster API (any)">}}

```yaml
Expand Down
Binary file not shown.
Loading
Loading