-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add workflow to use loadbalancer as a tunnel to juju controller on k8s #314
Conversation
push: | ||
branches: | ||
- "main" | ||
paths-ignore: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add CHANGELOG.md
and the examples
directory for both cases of pull_request and push. We should do that for all the workflows really.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cderici this one needs to be resolved please
.github/workflows/k8s_tunnel.yml
Outdated
echo "JUJU_USERNAME=$(juju show-controller | yq .$CONTROLLER.account.user)" >> $GITHUB_ENV | ||
echo "JUJU_PASSWORD=$(cat ~/.local/share/juju/accounts.yaml | yq .controllers.$CONTROLLER.password)" >> $GITHUB_ENV | ||
echo "JUJU_CA_CERT<<EOF" >> $GITHUB_ENV | ||
juju show-controller | yq .$CONTROLLER.details.ca-cert >> $GITHUB_ENV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where do juju install and juju bootstrap happen?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the charmed-kubernetes/actions-operator@main
action
9f90daa
to
e22feda
Compare
This is doing preciely the same scenario that's explained in https://discourse.charmhub.io/t/a-generic-way-to-communicate-with-a-juju-controller-on-a-k8s-cluster-with-the-juju-terraform-provider/10967
e68a721
to
ce82d7c
Compare
Description
This is doing precisely the same scenario that's explained in this discourse post.
Roughly the steps are:
Type of change
Environment
Juju controller version: 2.9
Terraform version: 1.5
QA steps
No manual QA needed, just check that the github action is doing what it supposed to do.
Additional notes
JUJU-3918