Skip to content

Add submodule to set up ACM #268

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

Closed
morgante opened this issue Sep 24, 2019 · 2 comments · Fixed by #324
Closed

Add submodule to set up ACM #268

morgante opened this issue Sep 24, 2019 · 2 comments · Fixed by #324
Assignees
Labels
enhancement New feature or request

Comments

@morgante
Copy link
Contributor

morgante commented Sep 24, 2019

We should add a new submodule which can be used to install ACM on a cluster.

This would involve:

  1. Deploying the ACM operator
  2. Automatically creating an SSH keypair for the operator, uploading it to the cluster (as a secret)
  3. Configuring the operator by creating a ConfigManagement resource in the cluster with these required values filled in:
  • spec.clusterName
  • spec.git.syncRepo
  • spec.git.secrectType (hardcode to ssh to start)
  • spec.git.policyDir

The module inputs should include:

  • cluster ID/self-link
  • sync repo
  • policy directory
  • sync branch (default master)

Outputs should include:

  • SSH public key (to give the cluster access to git)
@aaron-lane aaron-lane added the enhancement New feature or request label Sep 25, 2019
@kopachevsky
Copy link
Contributor

Biggest obstacle implementing this feature is lack of CRD support in terraform provider hashicorp/terraform-provider-kubernetes#215
workaround would be to do stuff with local-exec to run
kubectl apply -f config-management-operator.yaml

@morgante
Copy link
Contributor Author

morgante commented Oct 2, 2019

Yes, we can use local-exec + kubectl, following the existing pattern.

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

Successfully merging a pull request may close this issue.

3 participants