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

Extensions: Test the ability for the extensions operator to handle extension assets as tgz #13200

Open
aalves08 opened this issue Jan 24, 2025 · 0 comments

Comments

@aalves08
Copy link
Member

Is your feature request related to a problem? Please describe.

There's a new dev Rancher image (ping me for details/access) with a change that adds a new field compressedEndpoint in the UIPlugin CRD that can point to a tgz file. Handling extensions assets on the operator side compressed via tgz is a major performance enhancement that requires testing before we commit to the work of updating our build process.

Gameplan would be something like:

  • Find a way to test dev image provided to see if all works well with the tgz
  • If test looks good, update our build process to include the compressed tgz as an asset of an extension. We need to continue with the non-compressed assets as well as an alternative + supporting current published assets

Describe the solution you'd like

Describe alternatives you've considered

Additional context

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 24, 2025
@aalves08 aalves08 added QA/None and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant