Open tppalani opened 8 months ago
kubeadmConfigPatches: - | kind: InitConfiguration nodeRegistration: kubeletExtraArgs: node-labels: "ingress-ready=true" - | apiServer: extraArgs: runtime-config: "api/all=true" - | apiServer: extraArgs: admission-control: "ServiceAccount,NodeRestriction,PodSecurityPolicy,AlwaysAdmit" - | apiServer: extraArgs: apiserver.oidc-issuer-url: "https://dev-123456.okta.com/oauth2/default" apiserver.oidc-client-id: "ohaja1234mkalLMN" apiserver.oidc-username-prefix: "oidc:" apiserver.oidc-username-claim: "sub" apiserver.oidc-groups-prefix: "oidc:" apiserver.oidc-groups-claim: "groups"
This isn't quite right, your patches except the first one are not targeting any particular object so they're doing nothing.
You can just combine these into one patch, remove the -|
lines except the first one and merge the extraArgs into one map
/remove-kind bug /kind support
I'm running kind cluster in windows Operating system, Just for POC purpose i have optioned Okta CLIEND-ID and Okta Domain to enable to okta login mechanism . while creating cluster i have passed below configuration in yaml as extra api server configuration. But i don't see any effect after creating kind cluster. Even i verified kueb-apiserver.yaml file too but i don't see any configuration when i'm checking inside the container path:
cat ./kube/config
What you expected to happen: OIDC user will pick when i'm running below command
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kind version: (use
kind version
): kind v0.18.0 go1.20.2 windows/amd64Runtime info: (use
docker info
orpodman info
): $ podman info host: arch: amd64 buildahVersion: 1.33.2 cgroupControllers:OS (e.g. from
/etc/os-release
): windowsKubernetes version: (use
kubectl version
): Client Version: v1.28.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.27.1Any proxies or other special environment settings?: NA