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

Documentation request for oci cloud controller manager #42

Open
sorvis opened this issue Aug 31, 2022 · 1 comment
Open

Documentation request for oci cloud controller manager #42

sorvis opened this issue Aug 31, 2022 · 1 comment

Comments

@sorvis
Copy link

sorvis commented Aug 31, 2022

Starting down the path to utilize oci cloud controller manager so I thought perhaps this could be a good stepping stone for this project to document how to do it manually.

It mentions here the "--cloud-provider=external" and "--provider-id=" flag
https://github.com/oracle/oci-cloud-controller-manager#preparing-your-cluster

I think that would be set here on this line?

command = "kubectl --kubeconfig=kubeconfig config set-cluster kubernetes --server=https://${oci_core_instance._[1].public_ip}:6443"

But if my cluster is already provisioned then I could apply a config map to the kube-system namespace.
https://www.ibm.com/docs/en/cloud-private/3.1.0?topic=scaling-reconfiguring-kubelet-in-live-cluster

See also:
https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/

Any thoughts on the approach / does any one have another way to do this?

@jpetazzo
Copy link
Owner

I don't have experience setting up the OCI CCM, but I imagine that it'll require:

  • adding a few flags to kubelet / API server
  • running the CCM itself

Since we're using kubeadm to deploy the kubelets and the control plane, the flags may be passed through a kubeadm configuration file.

A good approach would be to add an extra Terraform variable to control whether to enable all these things or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants