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

common automatic update #120

Merged

Conversation

mbaldessari
Copy link
Contributor

  • feat: add support for hive clusterdeployments creating spokes
  • test: regenerated tests after clusterdeployment commit
  • test: updated test-cased and regeneated expectations
  • chore: added annotations controling gitops and fail for missing meta for clusterdeployments
  • chore: removed managedclusterset spec
  • Added support to label/annotate nodes
  • Added support to enable user workloads in control plane nodes
  • Added full support for the scheduler
  • Simplified PR for auto approve install plans
  • fix: when using clusterdeployments, secrets should exist in the cluster-namespace
  • bug: Invalid OperatorGroup generated when ommitting targetNamespaces
  • Fix CI issue
  • Actually use adminServiceAccountName for the auto approve job
  • Make sure that the if condition on chart split is not always true
  • Bump super-linter from 5 to 6
  • Drop some validations for now
  • Add some debugging to the chart split action
  • Use a specific git version when running git subtree split
  • Release clustergroup v0.8.6
  • Add a sudo to apt-get command
  • Add some READMEs in the individual charts
  • Fix super-linter issues and upgrade local super-linter target
  • Skip unreachable spokes when setting up vault
  • Add no_log to spokes initialization task
  • Drop initContainers variable and make it the default
  • Update tests after dropping initContainers
  • Release clustergroup v0.8.7
  • Upgrade ESO to v0.9.19
  • Update helm version in CI to 3.14.0
  • Drop imperative.initcontainers.gitinit
  • Have unseal work whenever we specifiy HEAD
  • make resourceExclusion configurable
  • Update tests after upgrading resourceExclusions tweak
  • Make resourcehealthchecks configurable
  • Update tests after upgrading resourceHealthChecks change
  • Do not quote $BRANCH variable
  • Fix initcontainer race on spokes
  • Release clustergroup v0.8.8
  • configure annotation based resource tracking
  • Drop imperative.volumes and imperative.volumemounts
  • Properly quote vault kv command
  • Make HUB work when spokes point to in hub cluster gitea
  • update tests
  • ACM chart version 0.0.2
  • golang-external-secrets chart version 0.0.4
  • hashicorp-vault chart version 0.0.2
  • Implement multi-source
  • Add tests for proper multisource support on spokes
  • Release clustergroup v0.8.9
  • Fix multisource indent error
  • Release clustergroup v0.8.10
  • Release acm v0.0.3
  • Fix missing chart field
  • Release acm v0.0.4
  • Update chart versions
  • Update vault-helm to v0.28.1 and vault to 1.17.2
  • Update ESO to 0.9.20
  • Release new hashicorp-vault and golang-external-secrets charts
  • Add Ansible playbook
  • Put the playbook in a more normal location for us
  • Exclude new playbook
  • Allow for choice in where file is written
  • Fix pki bind mount when using podman machine
  • Update tests after common rebase

TomerFi and others added 30 commits April 16, 2024 19:16
Co-authored-by: Alejandro Villegas <alex.ansi.c@gmail.com>
Signed-off-by: Tomer Figenblat <tfigenbl@redhat.com>
Co-authored-by: Alejandro Villegas <alex.ansi.c@gmail.com>
Signed-off-by: Tomer Figenblat <tfigenbl@redhat.com>
Co-authored-by: Alejandro Villegas <alex.ansi.c@gmail.com>
Signed-off-by: Tomer Figenblat <tfigenbl@redhat.com>
…for clusterdeployments

Signed-off-by: Tomer Figenblat <tfigenbl@redhat.com>
Signed-off-by: Tomer Figenblat <tfigenbl@redhat.com>
…er-namespace

Co-authored-by: Michele Baldessari <michele@acksyn.org>
Co-authored-by: Alejandro Villegas <alex.ansi.c@gmail.com>
Signed-off-by: Tomer Figenblat <tfigenbl@redhat.com>
Problem Statement:
When setting a namespace like this:
    - openshift-distributed-tracing:
        operatorGroup: true
        targetNamespaces: []

The chart generates the following yaml:
```yaml
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: openshift-distributed-tracing-operator-group
  namespace: openshift-distributed-tracing
spec:
  targetNamespaces:
```

Which k8s rejects the targetNamespaces key as invalid when it attempts to apply it and removes it since it doesn't have a value, which just so happens to have the desired result of not setting the targetNamespaces (or a selector) to enable it for All Namespaces.
bug: Invalid OperatorGroup generated when omitting targetNamespaces
feat: use hive clusterdeployment for creating spoke clusters
…sters

Added support to control the scheduler/cluster spec
Actually use adminServiceAccountName for the auto approve job
This should fix the fact that jobs are triggered on unrelated changes
Make sure that the if condition on chart split is not always true
Add some debugging to the chart split action
Otherwise we will get errors during the command as git subtree has
regressed since v2.44.0
Use a specific git version when running git subtree split
mbaldessari and others added 29 commits June 29, 2024 19:13
Update vault-helm to v0.28.1 and vault to 1.17.2
Release new hashicorp-vault and golang-external-secrets charts
Currently we test for the existance of local TLS folder and bind mount
them in containers. This does not work correctly when using podman
machine, because a the test is running on the host and so we might bind
mount the wrong folder. For example:
On Mac OSX /etc/pki does not exist on the folder and so we bind mount
/etc/ssl even though /etc/pki does exist in the podman machine VM

Co-Authored-By: Ákos Erős <aeros@redhat.com>
Fix pki bind mount when using podman machine
@mbaldessari mbaldessari merged commit 0d7d334 into validatedpatterns:main Aug 6, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants