changes from upstream - #1
Open
kamilchociej wants to merge 69 commits into
Open
Conversation
This dashboard was replaced by the pulsarheartbeat dashboard. It currently causes a conflict in Grafana due to the duplicate UID.
Rename `heap size` label to `committed` to match the metric being used.
… plaintext/TLS (#176) Merged, thanks!
…by appending existing options (#179) * Added JAVA_OPTS as an env variable * Updated JAVA_OPTS
This reverts commit 78e6675.
This reverts commit 2d4f8c1.
* Fix final docker tags * Use local variables
* Fix Integration Tests * Fix LICENSE Checks
Add support for minAvailable in PDB [STREAM-591]
* Add Cluster Scope * Fix Namespacing permissions * Fix Single namespace * Fix K8s test case * Update pom.xml * Add Test for Cluster Scope operator * Fix Multiple namespaces * Fix Multiple namespaces * Fix Multiple namespaces * Fix Multiple namespaces * Fix Multiple namespaces * Upgrade helm chart to 0.3.2
…ts (#194) * initial commit for securityContext * Updated resourcesFactories with securityContext to the builders of statefulsets/deployments * preserve previous behaviour of default securityContext * CRDs and api-reference.md update using pre-commit script * updated to allow subset of values of securityContext using SecurityContextConfig.java * pre-commit.sh * fixed NPE * fix tests as previously it is programatically coded. * ordering change for matching the yaml * pulsar CR test yaml update * confluent kafka latest versions are not working with pulsar
* [maven-release-plugin] prepare release operator-0.3.4 * [maven-release-plugin] prepare for next development iteration
* updated default values.yaml image of kaap * Release kaap chart 0.3.4
* [feature] Add loadBalancerClass support to proxy and pulsar CRDs * update api-reference.md
* upgrade quarkus and k8s client - upgrade quarkus 5.1.4 -> 6.9.3 - upgrade k8s client 6.3.1 -> 6.14.0 - update javax packages to jakarta - regenerate CRDs * dev mode now requires CRDs to be applied by quarkus itself. * reverting the change to patchStatus because of failure * quarkus maven plugin version should be compatible with the sdk * downgrade fabric8 to 6.13.4 for quarkus compatibility * helm based tests are not applying rbac manifests but trying to delete them. * remove sundr and jackson dependency management - crd generator switched from sundrio to jackson - jackson dependencies are now managed by fabric8 * duplicate nodeselectors test fix --------- Co-authored-by: sandeep-ctds <ext-sandeep.malla@datastax.com>
* [maven-release-plugin] prepare release operator-0.4.1 * [maven-release-plugin] prepare for next development iteration
* Update default operator image version to 0.4.1 * Release kaap chart 0.4.1
This fixes an issue when using skip_packaging=true Use a commit hash for the version until there is a new release of the action. helm/chart-releaser-action#171 The commit hash being used is helm/chart-releaser-action@3e001cb
Co-authored-by: mukesh-ctds <mukesh150497@gmail.com>
* update grafana example to include persistence * fixes from comments decrease dashboard volume size allow dashboard updates
Use the API calls to check for Deployment readiness instead of checking via matching replicasets.
* upgrade JDK to 21 - upgrade JDK from 17 to 21 - fix compile errors with java 25 - fix some compiler warnings Since JDK 23, the maven compiler plugin needs to have lombok annotations explicitly enabled. https://inside.java/2024/06/18/quality-heads-up/ * upgrade spotbugs and fix issues
* upgrade kube-prometheus-stack Note: due to an issue in the grafana Helm chart, we can't upgrade to a more recent version (grafana/helm-charts#3699) * update grafana dashboards update all Pulsar dashboards to use newer timeseries component (instead of deprecated graph) fix a few naming inconsistencies
Check for multiple 'component' labels for bookkeepers to allow for more than one bookkeeper statefulset.
* Release kaap chart 0.4.2 * Release kaap stack chart 0.4.2 * update the image version in Helm values when releasing the Helm chart * gracefully handle cases where there are no additional doc changes
* STREAM-799: [fix] CVEs found in KAAP operator and OpenJDK * New Snyk vul resolved.
* [maven-release-plugin] prepare release operator-0.4.3 * [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release operator-0.4.4 # Conflicts: # migration-tool/pom.xml # operator-common/pom.xml # operator/pom.xml # pom.xml # tests/pom.xml * [maven-release-plugin] prepare for next development iteration
* updated tls config to include acme * Updated CertManagerCertificatesProvisioner.java to process the acme config and generate certificates * Added support for multiple challenge solvers * Refactored duplicate code for validation * Added external certificate support for ACME * minor fix when generate is false on external services. * pre-commit and checkstyle * moved from deprecated createOrReplace to serverSideApply with forceConflicts * test fix for forceConflicts() Update the annotation to jupiter to allow it to run in CI * updated rbac rules for cert-manager issuers and certificates to include patch * added unit test for the acme certificate generation flow
* Add support for minReadySeconds to all kaap CRs * Update api-reference.md doc and all the kaap CRs
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
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.
No description provided.