Ciprian Hacman
Ciprian Hacman
Technically, creating a new cluster should give you some other random IP. I don't think there's anything important there yet. 😄
kOps has a feature that lets you configure mirrors for container images and files: https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#AssetsSpec If you configure `fileRepository` and `containerRegistry` you should be able to copy all the things...
As a workaround, could you try using `--dns=none` when creating the cluster?
This was somehow lost as part of the mitigation for https://github.com/kubernetes/kops/issues/15539. See this comment for guidance on on how to switch: https://github.com/kubernetes/kops/pull/15643#issuecomment-1637151077.
CC @zetaab
Please explain the problem in detail: * Which is the version of kOps it last worked with? * What is the difference between the kubeconfig generated by the working version...
> Cluster was created with 1.26.3 binary and then the config was exported with 1.25.4. binary. In that case it worked, so in config there were no changes. What is...
Where did `https://internal.cluster-api.control.example.com:8443` come from? Do you also change `MasterInternalName` somewhere?
I still don't understand where you get the `https://internal.cluster-api.control.example.com:8443`. The internal address of the API server is `api.internal.`.
As of 1.26, changing `masterInternalName` is no longer allowed. `kops export kubecfg --admin --internal` will always set `server: https://api.internal.cluster-api.control.example.com`. Please try to use `additionalSANs` instead, if that's possible with your...