Sure that makes sense ... was just thinking the Log4J CVE would warrant a change here but easy enough for people to upgrade the image!
On Thu, Mar 17, 2022 at 10:08 AM Houston Putman <[email protected]> wrote: > > Unfortunately that would require a re-spin. We are going to start using the > official SVN releases as the official helm chart location soon (which is a > major win, but we can't really go and change things after the fact anymore). > > The default version is upgraded to 8.11 on main (v0.6.0), but I decided > against upgrading it on 0.5.1 mainly due to the impact vs what is expected > from a bug-fix upgrade. > Personally I think that users should expect little to change in bug-fix > releases besides obviously bugs being fixed. > So if their Solr instances suddenly change versions, that seems a little > heavy handed to me (though it would only happen for new solr clusters, not > existing ones... Maybe I was overthinking this) > > I do hope that we can get v0.6.0 out in a month or so, because it should come > with some very needed improvements. > > On Thu, Mar 17, 2022 at 12:00 PM Timothy Potter <[email protected]> wrote: >> >> +1 (binding) >> >> Ran the smoke tester and deployed on Docker Desktop. >> >> BTW: Is it possible to change the Solr version deployed from the Helm >> chart to 8.11.1 w/o a respin of the RC? It's still deploying Solr 8.9 >> (easy enough to upgrade the Docker image if not) >> >> Cheers, >> Tim >> >> On Wed, Mar 16, 2022 at 12:04 PM Jason Gerlowski <[email protected]> >> wrote: >> > >> > +1 >> > >> > Smoke tester passes for me, as did some manual testing. >> > >> > (Testing was mostly focused on local and GCS backups, with some >> > attention paid to general use.) >> > >> > On Tue, Mar 15, 2022 at 4:49 PM Houston Putman <[email protected]> wrote: >> > > >> > > Please vote for release candidate 2 for the Solr Operator v0.5.1 >> > > >> > > The artifacts can be downloaded from: >> > > https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.1-RC2-revafa762893f16857b86b2ae9fc5365d21ada49a29 >> > > >> > > You can run the full smoke tester, with instructions below. >> > > However, it is also encouraged to go and use the artifacts yourself in a >> > > test Kubernetes cluster. >> > > The smoke tester does not require you to download or install the RC >> > > artifacts before running. >> > > If you plan on just running the smoke tests, then ignore all other >> > > instructions. >> > > >> > > The artifacts are layed out in the following way: >> > > * solr-operator-v0.5.1.tgz - Contains the source release >> > > * crds/ - Contains the CRD files >> > > * helm-charts/ - Contains the Helm release packages >> > > >> > > The RC Docker image can be found at: >> > > apache/solr-operator:v0.5.1-rc2 >> > > >> > > The RC Helm repo can be added with: >> > > helm repo add apache-solr-rc >> > > https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.1-RC2-revafa762893f16857b86b2ae9fc5365d21ada49a29/helm-charts >> > > >> > > You can install the RC Solr Operator and Solr CRDs and an example Solr >> > > Cloud with: >> > > curl -sL0 "https://dist.apache.org/repos/dist/release/solr/KEYS"; | gpg >> > > --import --quiet >> > > # This will export your public keys into a format that helm can >> > > understand. >> > > # Skip verification by removing "--verify" in the helm command below. >> > > if ! (gpg --no-default-keyring --keyring=~/.gnupg/pubring.gpg >> > > --list-keys "98F3F6EC"); then gpg --export >~/.gnupg/pubring.gpg; fi >> > > kubectl create -f >> > > https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.1-RC2-revafa762893f16857b86b2ae9fc5365d21ada49a29/crds/all-with-dependencies.yaml >> > > || \ >> > > kubectl replace -f >> > > https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.1-RC2-revafa762893f16857b86b2ae9fc5365d21ada49a29/crds/all-with-dependencies.yaml >> > > helm install --verify solr-operator apache-solr-rc/solr-operator --set >> > > image.tag=v0.5.1-rc2 >> > > helm install --verify example apache-solr-rc/solr >> > > >> > > You can run the full smoke tester directly with this command: (First >> > > checkout the release-0.5 branch of the solr-operator) >> > > >> > > ./hack/release/smoke_test/smoke_test.sh -v "v0.5.1" -s "afa7628" -i >> > > "apache/solr-operator:v0.5.1-rc2" -g "98F3F6EC" \ >> > > -l >> > > 'https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.1-RC2-revafa762893f16857b86b2ae9fc5365d21ada49a29' >> > > >> > > If you want to run the smoke test with a specific version of kubernetes, >> > > use the -k option with a full version tag. (e.g. -k v1.19.3) >> > > If you want to run the smoke test with a custom version of solr, use the >> > > -t option with an official Solr image version. (e.g. -t 8.10.0) >> > > However, for this smoke test, you must use a solr version that >> > > supports incremental backups. (i.e. 8.9+) >> > > >> > > Make sure you have the following installed before running the smoke test: >> > > - Docker (Give it enough memory and CPU to run ~12 containers, 3 of >> > > which are Solr nodes) >> > > More information on required resources can be found here: >> > > https://kind.sigs.k8s.io/docs/user/quick-start/#settings-for-docker-desktop >> > > - Go 1.17 >> > > - Kubectl >> > > - GnuPG >> > > - Helm v3.4.0+ >> > > - Kustomize (v4.0.0+) This will be installed for you, but NOT upgraded >> > > if a lower version is already installed. >> > > - yq >> > > - jq >> > > - coreutils (if using Mac OS) >> > > >> > > The vote will be open for at least 72 hours i.e. until 2022-03-18 21:00 >> > > UTC. >> > > >> > > [ ] +1 approve >> > > [ ] +0 no opinion >> > > [ ] -1 disapprove (and reason why) >> > > >> > > Here is my +1 >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
