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

Make the Docker image with all plugins the default image #4275

Closed
4 of 5 tasks
anna-geller opened this issue Jul 8, 2024 · 4 comments
Closed
4 of 5 tasks

Make the Docker image with all plugins the default image #4275

anna-geller opened this issue Jul 8, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request kind/breaking-change Code modifications needed before upgrading

Comments

@anna-geller
Copy link
Member

anna-geller commented Jul 8, 2024

Feature description

The plan

  1. Rename latest-full to latest so that all plugins are included in the default image displayed at the top in DockerHub
    image

  2. Rename the current latest to latest-no-plugins with no plugins included.

  3. Adjust the CI/CD and release processes to use kestra/kestra:develop instead of kestra/kestra:develop-full. Add kestra/kestra:develop-no-plugins.

  4. Adjust the CI/CD and release processes to use kestra/kestra:v0.18.0 instead of kestra/kestra:v0.18.0-full. Add kestra/kestra:v0.18.0-no-plugins

Impact

  • Users who leverage the latest image will need to change the image in their deployment before upgrading to latest-no-plugins if they prefer to have only their custom plugins. We should make that Breaking Change very clear in the Release Notes
  • Adjust all Getting Started and Installation docs afterward to use the kestra/kestra:latest instead of kestra/kestra:latest-full
  • Adjust the main GitHub README
  • Adjust Helm Charts README and deployment guides
  • Adjust Zendesk guides to use new images #4580
@anna-geller anna-geller added enhancement New feature or request kind/breaking-change Code modifications needed before upgrading labels Jul 8, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Issues Jul 8, 2024
@loicmathieu
Copy link
Member

The same should be done for all tags: develop/develp-full and v0.18.0/v0.18.0-full (and all future version tags).

@anna-geller
Copy link
Member Author

extra TODO: let's check if we can then merge or close this PR kestra-io/validate-action#1

@anna-geller
Copy link
Member Author

@anna-geller anna-geller moved this from Backlog to In progress in Issues Aug 5, 2024
@loicmathieu
Copy link
Member

loicmathieu commented Aug 5, 2024

@Skraye after the release the following PRs needs to be merged:

I'll add more to the list if I saw other repo that needs to be impacted.

@anna-geller anna-geller moved this from In progress to In review in Issues Aug 6, 2024
@github-project-automation github-project-automation bot moved this from In review to Done in Issues Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request kind/breaking-change Code modifications needed before upgrading
Projects
Archived in project
Development

No branches or pull requests

2 participants