Document howto enable deprecated k8s APIs

[nbartos]

For kubeadm I can do something like this to enable the deprecated APIs in k8s 1.16:

apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
apiServer:
  extraArgs:
    runtime-config: "apps/v1beta1=true,apps/v1beta2=true,extensions/v1beta1/daemonsets=true,extensions/v1beta1/deployments=true,extensions/v1beta1/replicasets=true,extensions/v1beta1/networkpolicies=true,extensions/v1beta1/podsecuritypolicies=true"

How would I go about creating a kind 1.16 cluster with these APIs enabled?

[neolit123]

kind supports patches for the kubeadm configuration:
https://kind.sigs.k8s.io/docs/user/quick-start/#enable-feature-gates-in-your-cluster

/triage support
/kind documentation

[nbartos]

Thanks, adding this to the config seems to work:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  kubeadmConfigPatches:
  - |
    apiVersion: kubeadm.k8s.io/v1beta2
    kind: ClusterConfiguration
    apiServer:
      extraArgs:
        runtime-config: "apps/v1beta1=true,apps/v1beta2=true,extensions/v1beta1/daemonsets=true,extensions/v1beta1/deployments=true,extensions/v1beta1/replicasets=true,extensions/v1beta1/networkpolicies=true,extensions/v1beta1/podsecuritypolicies=true"

I think this is a fairly common use case, having it in the docs would be nice.

[neolit123]

Thanks, adding this to the config seems to work

excellent.

I think this is a fairly common use case, having it in the docs would be nice.

docs PRs are always welcome.

[BenTheElder]

with kind v0.7.0 you can do the following kind config:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
kubeadmConfigPatches:
- |
  kind: ClusterConfiguration
  apiServer:
    extraArgs:
      runtime-config: "apps/v1beta1=true,apps/v1beta2=true,extensions/v1beta1/daemonsets=true,extensions/v1beta1/deployments=true,extensions/v1beta1/replicasets=true,extensions/v1beta1/networkpolicies=true,extensions/v1beta1/podsecuritypolicies=true"

which will work for v1beta1 and v1beta2 kubeadm versions.

I think I'm probably going to add a first-class field for runtime config as it's frequently in need of patching across versions and document that instead though.

[BenTheElder]

#1816 documentation will follow this first-class runtimeConfig option

[ghost]

Hi, I am interested to work on this.

I think adding above examples (#1271 (comment) and #1271 (comment) ) and some explanations needed in the page Getting Started page: https://github.com/kubernetes-sigs/kind/blob/master/site/content/docs/user/quick-start.md#enable-feature-gates-in-your-cluster

[BenTheElder]

kind v0.9.0+ has a runtimeConfig option now. It is documented at https://kind.sigs.k8s.io/docs/user/configuration/#runtime-config

A note about enabling / disabling k8s APIs probably belongs here.

[atoato88]

Is this issue still open?

As @BenTheElder says in previous comment, there is a contents about runtimeConfig at here.
So I think this issue can be closed, but I think that it's friendly to write more details about specifing multiple APIs discussed here.

update site/content/docs/user/configuration.md as follows:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
runtimeConfig:
+  # You can specify multiple APIs.
  "api/alpha": "false"
+  "api/beta": "true"
+ ...

If it's OK, I will create PRs update like that.

[BenTheElder]

i think showing multiple sounds good. we should probably specifically mention enabling a deprecated API though per this issue, though increasingly that will not be available in kubernetes anyhow as there's been effort to stabilize the APIs and move to GA + remove anything still deprecated ...

[atoato88]

Yes, I agree with your comments.
My intent was just more detailed yaml structures about runtimeConfig.

Sorry for my comment if my comment isn't target for this PR.