Releases: instana/instana-agent-operator
Releases · instana/instana-agent-operator
v1.0.0
Upgrade quarkus from 1.2.1.Final to 1.9.0.Final
- The main change here is the version bump of quarkus from 1.2.1.Final to 1.9.0.Final and all the necessary code changes for it to compile.
- The other change to point out is that we had to add the
createpermissions to theinstana.ioapiGroup in the Operator'sClusterRoleininstana-agent-operator.yaml. This is due to a change in[kubernetes-client](https://github.com/fabric8io/kubernetes-client/issues/2292)when callingcreateOrReplace, it will first try acreateand if it fails with a conflict exception, then it'll try anupdate, which means that the operator will needcreatepermissions in theinstana.ioapiGroup - Include the version of the
instana/instana-agent-operatorimage tag in the generatedinstana-agent-operator.yamlto help ensure that the operators using a previous tag would still work if we introduce a breaking change in a new operator image that requires an updatedinstana-agent-operator.yaml - No longer pushing the
latesttag for the operator image in order to tie the operator yaml updates more closely with the operator image updates and avoid the situation where the customers are pulling the latest operator image containing a breaking change but not explicitly updating the operator yaml
v0.3.10
Upload RedHat Operator bundle automatically for full release tags (#45) ## Why RedHat has recently changed the process for updating a new version of the operator. One of the last steps of this process was to upload the operator bundle, which includes some metadata and manifests in the form of yaml files. This used to be a manual process by which we would upload a zip file at this location: https://connect.redhat.com/project/3928601/operator-metadata. However, there is now an Operator Bundle project https://connect.redhat.com/project/5791371/images, where you can upload a docker container image containing the same files. Therefore, we should perform this last step automatically instead of having to remember to do this manually. ## What Update the Jenkins pipeline to download all the assets for a specific GitHub Release (so as to not assume that those assets are available on hand, for when we do move this pipeline to Concourse and each pipeline job being run in a separate container with a clean slate). Then unzip the specific `redhat-<version>.zip` file, build a docker container containing those files in that zip directory, and upload that container image to the RedHat registry so it shows up in the `Instana-Agent-Operator-Bundle` project: https://connect.redhat.com/project/5791371/images
v0.3.9
Copy metadata files for RedHat artifacts without the '-r' flag. According to the man page for 'cp': Historic versions of the cp utility had a -r option. This implementation supports that option; however, its use is strongly discouraged, as it does not correctly copy special files, symbolic links, or fifo's.
