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

Organize CoreDNS and kube-proxy manifests so they're optional #386

Merged
merged 1 commit into from
May 13, 2024

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented May 12, 2024

  • Add components variable to configure CoreDNS and kube-proxy manifests. Allow provisioning clusters without CoreDNS or kube-proxy by disabling these components, so they can be customized or managed through separate plan/apply processes or automation
# default
components = {
  enable = true
  coredns = {
    enable = true
  }
  kube_proxy = {
    enable = true
  }
}

* Add a `coredns` variable to configure the CoreDNS manifests,
with an `enable` field to determine whether CoreDNS manifests
are applied to the cluster during provisioning (default true)
* Add a `kube-proxy` variable to configure kube-proxy manifests,
with an `enable` field to determine whether the kube-proxy
Daemonset is applied to the cluster during provisioning (default
true)
* These optional allow for provisioning clusters without CoreDNS
or kube-proxy, so these components can be customized or managed
through separate plan/apply processes or automation
@dghubble dghubble merged commit 9902860 into main May 13, 2024
1 check passed
@dghubble dghubble deleted the reorganize branch May 13, 2024 04:17
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

Successfully merging this pull request may close these issues.

1 participant