Skip to content

Conversation

@robhabraken
Copy link

The Kubernetes specification files as provided contain a hard-coded connection string to Redis. You can of course change it in there (the cd.yaml spec file in your repo), but I think it is more elegant to remove the value from the specification files and place it inside a secrets file, as is being done with the Solr connection string. This makes the spec file implementation-agnostic, easier to upgrade and not containing environment specific variables / parameters. Subsequently, you can choose to retrieve this connection string value either from an Azure DevOps Variable group, or by using a secret from your Azure KeyVault instance for example, to inject the correct value in the secrets file at provisioning-time.

I also mentioned this in my blog post https://www.robhabraken.nl/index.php/3619/paas-to-aks-arm-for-eds/, this is the corresponding Pull Request of said change to the spec files.

…parate K8s secret to allow for easier population of custom connection string
@robhabraken robhabraken requested a review from a user December 17, 2020 14:31
@bplasmeijer bplasmeijer added the enhancement New feature or request label Dec 17, 2020
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Thanks for your input @robhabraken.

We will however reject this PR, as we do not accept PR's to this repo master branch (please see the README). The reason being that source is actually hosted internally, this repo is only used to publish released versions.

We might consider creating a separate "contrib" branch in the future for input and suggestions. However this has not been decided yet.

I have asked the team to look at and evaluate your proposal.

@robhabraken
Copy link
Author

Thanks Jonas! I only saw this remark in the README after submitting my PR. Thanks for evaluating my proposal and looking forward to a contrib branch!

@bplasmeijer
Copy link
Member

@michaelbaranov can you share with the container team.

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

Successfully merging this pull request may close these issues.

3 participants