- publish only binaries instead of a tar.gz of the binaries bundle
- create SBOM as part of the gorelease pipeline
- use github changelog for the release
- sign ALL the things. Binaries, checksum, and even the SBOM
- release also the cert+sig of the generated artifacts
Signed-off-by: Itxaka <igarcia@suse.com>
Enables deploying multiple operators replicas.
Changes tests to account and test this
Chart changes:
- Make any fixed names default to the release name. As release name has
to be unique per namespace, this is a good practice instead of
hardcoding whatever name we want. This shouldnt affect anything as
the full chart uses that by default now.
Signed-off-by: Itxaka <igarcia@suse.com>
Signed-off-by: Itxaka <igarcia@suse.com>
Stuff under dmidecode is part of the register command.
Also drops some old sutff unused from the ros-installer
Signed-off-by: Itxaka <igarcia@suse.com>
Signed-off-by: Itxaka <igarcia@suse.com>
Co-authored-by: Klaus Kämpf <kkaempf@suse.de>
* Produce 2 binaries instead of one
This generates a different binary for the register command as to not
bundle it with the full operator.
On the makefile separated builds have been done for operator and
registry.
On the docker image a different container is created for the register
and pushed to a different repo as well.
For releases gorelease generates 2 different binaries.
Signed-off-by: Itxaka <igarcia@suse.com>
We were restoring the cache of go always but we need to restore only if
the sha of the go.sum its the same, otherwise we need to recreate the
cache
Signed-off-by: Itxaka <igarcia@suse.com>
There seems to have some confusion between the namespace of the operator
to run on and the namespaces we want the operator to watch
This restores the sync_namespaces so the operator can watch all
namespaces and sets teh namespace option to be where the operator is
runnig, needed for things like the registration url to be properly
served
Signed-off-by: Itxaka <igarcia@suse.com>
Remove all the mentions to rancheros-operator in tests, imports and
dependencies.
Restore e2e scripts and test targets on makefile
Fix all lint issues
Signed-off-by: Itxaka <igarcia@suse.com>
* Move main into a cmd/operator package
* Add elemental-installer
* Adding installer unit tests
* Update Makefile
* Update .github/workflows/unit-tests.yaml
* Adapat Dockerfile and golreleaser to keep releasing and building elemental-operator as they used to
Signed-off-by: David Cassany <dcassany@suse.com>
Co-authored-by: Itxaka <igarcia@suse.com>
Co-authored-by: David Cassany <dcassany@suse.com>
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Co-authored-by: Ettore Di Giacinto <edigiacinto@suse.com>
Co-authored-by: David Cassany <dcassany@suse.com>
We were missing setting the proper repo and short tag on tag release and
were instead leaving the default values in there which made our released
chart point to the ci values with ci images
Instead point ot the proper repo and set the image tag of the chart to
the released tagged image (no commit or anything in the image)
Signed-off-by: Itxaka <igarcia@suse.com>
- Allow setting different image versions for kubernetes
- Set a matrix for kubernetes version on CI
- Use kubectl wait to wait for control panel to be ready
- Set default kubernetes version to latest rancher ready (v1.22.7)
Signed-off-by: Itxaka <igarcia@suse.com>
There was a mix of ros-operator and rancheros-operator.
This patch fixes it so its always rancheros-operator, even
changing the repos to have the full name so everything matches
Signed-off-by: Itxaka <igarcia@suse.com>
- Run it only under PRs for testing
- The docker job is the one that pushes the images tot he proper repo
- Integration will only push to the ros-operator-ci registry
Signed-off-by: Itxaka <igarcia@suse.com>
- Drops everything not needed for ros-operator
- New simple Dockerfile
- New jobs based on ros-operator only
- Remove uneeded tests
- Remove dependency on os2 images for integration tests
- Use gorelease to release ros-operator binaries
- Use docker to push ci images to ros-operator-ci registry on PR
- Use docker to push master/tag images to ros-operator registry
- Build chart indepently
- Have a null test CI job for future integration tests
Signed-off-by: Itxaka <igarcia@suse.com>
* ci: add installation test with Rancher
* ci: add auto-provisioning of the VM
* ci: install Rancher on GH runner
* ci: move rancher installation+configuration in scripts
* ci: define our own MachineRegistration
* ci: install generated RancherOS Operator chart
* ci: don't use default namespace for test cluster
* ci: add TPM device to VM
* ci: refactoring + add OS installation and config
* ci: use iPXE to install the OS
* ci: keep artifacts and cleanup at the end
* ci: use 'script -e -c` to simulate a TTY
* ci: add check on cluster creation
* ci: fix SERVER_ID
* ci: specify that RKE2 can be installed too
* ci: use container image on self-hosted runner
* ci: add missing packages in container
* ci: upload needed logs
* fix/ci: use quays.io and official repos
* fix/ci: '\n' is not needed when assigned to a var
* ci: move bootstrapping node test in tests folder
* ci: add 'make' package
Signed-off-by: Loic Devulder <ldevulder@suse.com>
Alexander Demicev