common automatic update #272
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
mbaldessari
commented
Sep 6, 2024
mbaldessari
commented
- Allow originRepo to be set via make install and main.git parameters
- resolves Eliminate out-of-sync conditions #21 rag-llm-gitops
- Fix vars that were erroneously dropped
- Allow more flexibility with multiSourceConfig schema
- Inject VALUES_SECRET env var
- Add helmRepoUrl variable
- Update letsencrypt to v0.1.1
- Allow overriding gitops source on spokes
- Update acm chart to v0.1.1
- Update clustergroup chart to 0.8.11
- Extend the schema for disconnected
- Update clustergroup chart to 0.8.12
- Update super-linter to v7
- Fix action path
- Fix action path v2
- Upgrade ESO to v0.10.0
- Upgrade vault to 1.17.3
- Update hashicorp-vault to 0.1.2
- Update golang-external-secrets to 0.1.2
- Switch to gitops-1.13
- Add a pushsecrets policy and vault path for ESO syncing
- Fix PyInk warnings
- Update tests after common rebase
We introduce the `main.git.repoUpstreamURL` parameter. This can be used to set `originRepo`. When `originRepo` is set, an in-cluster gitea will automatically be spawned. In this case `originRepo` will point to the upstream repository and `targetRepo` will point to the internal in-cluster gitea mirror.
resolves validatedpatterns#21 rag-llm-gitops
Allow originRepo to be set via make install and main.git parameters
In 98d4312 (Fix pki bind mount when using podman machine) we erroneously dropped some K8S_* variables. Reported-by: Andrew Beekhof <beekhof@redhat.com>
Fix vars that were erroneously dropped
We specifically also add helmRepoUrl as it make it more discoverable, but we stay flexible in what we accept so that things can be extended without having to be in lockstep with the operator.
Allow more flexibility with multiSourceConfig schema
Since it can be used to point to an alternative file, let's inject it into the container
Inject VALUES_SECRET env var
Add helmRepoUrl variable
Update letsencrypt to v0.1.1
This is needed on spokes when installing in a disconnected environment
A couple of small updated and new releases
Extend the schema for disconnected
Update clustergroup chart to 0.8.12
Update super-linter to v7
Upgrade ESO to v0.10.0
Upgrade vault to 1.17.3
Release new hashicorp-vault and golang-external-secrets charts
It is supported all the way back to OCP 4.12 Tested on sno hub + spoke successfully
Switch to gitops-1.13
See the README for more details, but TLDR: you can use
`secret/pushsecrets` to push secrets from any node to the vault.
This secret can then be retrieved from either a different namespace
or a different cluster node.
Tested this with a pushsecret as follows:
```
apiVersion: external-secrets.io/v1alpha1
kind: PushSecret
metadata:
name: pushsecret
namespace: hello-world
spec:
data:
- conversionStrategy: None
match:
remoteRef:
property: baz
remoteKey: pushsecrets/testme
secretKey: bar
deletionPolicy: Delete
refreshInterval: 10s
secretStoreRefs:
- kind: ClusterSecretStore
name: vault-backend
selector:
secret:
name: existing-secret
updatePolicy: Replace
```
The above takes the property called `baz` of an existing secret called `existing-secret` in
the `hello-world` namespace and pushes it to the `secret/pushsecrets/testme` vault path.
Suggested-By: Chris Butler <chbutler@redhat.com>
Closes: MBP-641
Add a pushsecrets policy and vault path for ESO syncing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.