Skip to content

Conversation

patelsmit32123
Copy link
Contributor

Issues Resolved

#1111

Check List

  • Commits are signed per the DCO using --signoff
  • Unittest added for the new/changed functionality and all unit tests are successful
  • Customer-visible features documented
  • No linter warnings (make lint)

If CRDs are changed:

  • CRD YAMLs updated (make manifests) and also copied into the helm chart
  • Changes to CRDs documented

Please refer to the PR guidelines before submitting this pull request.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@patelsmit32123 patelsmit32123 changed the title Use docker image's default startup command and install plugins via init container [WIP] Use docker image's default startup command and install plugins via init container Sep 30, 2025
Copy link

@josedev-union josedev-union left a comment

Choose a reason for hiding this comment

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

I know this is a draft PR and WIP now. Btw, small reminder for now.

Expect(pluginInstaller).ToNot(BeNil())
Expect(pluginInstaller.Command).To(ContainElement("/bin/bash"))
Expect(pluginInstaller.Command).To(ContainElement("-c"))
Expect(len(pluginInstaller.VolumeMounts)).To(Equal(0)) // No volume mounts needed

Choose a reason for hiding this comment

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

Need to make sure what paths we have to share with the main container to reflect the plugin installation.
Then use volume for that path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants