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

Kubernetes-addon namespaces can be specified and creation optional #595

Merged
merged 5 commits into from
Jun 30, 2022

Commits on Jun 24, 2022

  1. Allow namespace creation to be optional

    It's possible that the user may wish to deploy this to an existing
    namespace, or the kube-system namespace. That would not be possible,
    with the current configuration.
    bobdoah committed Jun 24, 2022
    Configuration menu
    Copy the full SHA
    c68962a View commit details
    Browse the repository at this point in the history
  2. IRSA module created namespaces should be optional

    Some of the addon modules create namespaces via the IRSA module. These
    should also be optional.
    bobdoah committed Jun 24, 2022
    Configuration menu
    Copy the full SHA
    b6861fa View commit details
    Browse the repository at this point in the history
  3. Ensure namespace is passed correctly to IRSA

    Some of the modules use the IRSA module, but don't create the namespace
    via that module. They need to pass the value set in the helm_config, so
    as to ensure both ServiceAccount and Helm chart are created in the same
    namespace.
    bobdoah committed Jun 24, 2022
    Configuration menu
    Copy the full SHA
    3f49a9e View commit details
    Browse the repository at this point in the history

Commits on Jun 30, 2022

  1. Configuration menu
    Copy the full SHA
    865d346 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    7fe5962 View commit details
    Browse the repository at this point in the history