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

[Cherry] Partially support the keystone-credentials relation enough to uplift the keystone service (#350) #351

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

addyess
Copy link
Member

@addyess addyess commented Jun 14, 2024

Cherry-pick to release 1.29 from #350

  • Partially support the keystone-credentials relation enough to uplift the keystone service
  • Adjust the failure mode when there's no keystone-auth-service
  • Improve kubectl() to error quicker when kubeconfig doesn't exist
  • Juju admin can configure authorization-webhook-config-file
  • charm-lib-kubernetes-snap back to main branch
  • AWS IAM provides a warning

…the keystone service (#350)

* Partially support the keystone-credentials relation enough to uplift the keystone service
* Adjust the failure mode when there's no keystone-auth-service
* Improve kubectl() to error quicker when kubeconfig doesn't exist
* Juju admin can configure authorization-webhook-config-file
* charm-lib-kubernetes-snap back to main branch
* AWS IAM provides a warning
Copy link
Member

@kwmonroe kwmonroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, +1 on this backport

@addyess addyess merged commit bb0d9d0 into release_1.29 Jun 14, 2024
7 checks passed
@addyess addyess deleted the cherry/350/release_1.29 branch June 14, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants