Not all additional objects are meant to be applied to the cluster; a
few are configured through a file path. We explicitly handle those
and don't write them to the file where they should be applied.
We check that users haven't specified the kubeconfig file path, as
this file is created / managed by kOps. We don't try to reuse the
upstream configuration validation, as this allows the user to specify
a partial configuration, and this means that we don't have to pull in
the upstream libraries.
We could in future accept the "correct" value or just treat providing
a value as a signal that kOps should not manage the file; for now we
are starting with the most restrictive configuration, as we can then
relax it in future if needed.
We generate a kube-scheduler configuration file in the kops CLI, and
nodeup will use it if provided (instead of generating one).
We put the configuration file into the fileAssets.
Users can provide a kube-scheduler configuration in additional
objects, and this will be used as the base configuration (we add the
kubeconfig path).
Issue #13352
Co-authored-by: Ciprian Hacman <ciprian@hakman.dev>
A combination of apiserver map handling when using server-side apply, CA injection and resource validation made it impossible for kops to remove this struct. However, kops should claim ownership of all fields so we can remove them all in a future version
The hook can cause issue on execution, like
```
Exec lifecycle hook ([/bin/sh -c rm -rf
/registration/ebs.csi.aws.com-reg.sock /csi/csi.sock]) for Container
"node-driver-registrar" in Pod
"ebs-csi-node-96jbk_ebs-csi(a82c6d41-bd2b-42dd-b092-e3acd4c43b62)"
failed - error: command '/bin/sh -c rm -rf
/registration/ebs.csi.aws.com-reg.sock /csi/csi.sock' exited with 126: ,
message: "OCI runtime exec failed: exec failed: container_linux.go:370:
starting container process caused: exec: \"/bin/sh\": stat /bin/sh: no
such file or directory: unknown\r\n"
```
Moreover, it has been deleted from upstream driver, see this patch
6e59160eea
Signed-off-by: Nicolas Sterchele <foss@sterchelen.net>
This will add tag all subnets with the IGs using that subnet
Update docs/operations/karpenter.md
Co-authored-by: Peter Rifel <rifelpet@users.noreply.github.com>