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

terraform: Update kubeflow-dashboard module ci + docs #236

Closed
orfeas-k opened this issue Sep 24, 2024 · 2 comments
Closed

terraform: Update kubeflow-dashboard module ci + docs #236

orfeas-k opened this issue Sep 24, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@orfeas-k
Copy link
Contributor

Context

Update terraform module CI and docs according to agreed convention in canonical/training-operator#200 (comment) where we agreed that:

  • Handling module compatibility in branches, that is, the module in Github branch track/1.8 of the training operator is compatible with that charm (1.8/stable, 1.8/edge), but the module in branch main is compatible with that charm (latest/edge).
  • Removing the note from the README.md as it will be obviated that there is a 1:1 compatibility mapping between the module and the charm in the same Github branch

What needs to get done

  • Remove the compatibility note from the README.md
  • Update the terraform-checks.yaml call to:
  • Backport the merged PR to 1.9-related branch while updating the
    terraform-checks.yaml call to deploy track/stable charm.

Definition of Done

Module in main has been updated and backported to 1.9-related branch.

@orfeas-k orfeas-k added the enhancement New feature or request label Sep 24, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6317.

This message was autogenerated

@orfeas-k
Copy link
Contributor Author

Closed by #237 and #238

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

No branches or pull requests

1 participant