Hi all, Thanks for kicking the tires in the last few days!
It's been >72h since the vote was initiated and the result is: +1 3 (3 binding) 0 0 -1 0 This vote has PASSED! I'll move forward with RC1 for the release! Best, Jason On Fri, Aug 12, 2022 at 7:01 PM Jan Høydahl <[email protected]> wrote: > > I tried the smoke tester, but I'm on M1 Mac and the go build complains about > > /Users/janhoy/go/pkg/mod/golang.org/x/[email protected]/unix/zsyscall_darwin_arm64.go:121:3: > too many errors > > Tried a few workarounds including installing a newer version of the module > but no luck. Don't have a Linux or x86 box handy right now. > > Jan > > > 12. aug. 2022 kl. 23:55 skrev Timothy Potter <[email protected]>: > > > > Just had time for the smoke tester this time, but +1 (binding) > > > > ******************** > > > > Local end-to-end cluster test successfully run! > > > > > > > > > > ******************** > > > > Successfully smoke tested the Solr Operator v0.6.0! > > > > On Fri, Aug 12, 2022 at 5:26 AM Jason Gerlowski <[email protected]> > > wrote: > >> > >> Hey all, > >> > >> Anyone else interested in voting or offering feedback on the RC? > >> > >> Best, > >> > >> Jason > >> > >> On Tue, Aug 9, 2022 at 6:42 PM Anshum Gupta <[email protected]> wrote: > >>> > >>> +1 (binding) > >>> > >>> Thanks for your effort, Jason. > >>> > >>> Smoke test passed and I did some manual testing w/ scaling etc. and > >>> everything seems to work as expected. > >>> > >>> I'd also like to share that I did run into issues when running with 'kind' > >>> version 0.9. Upgrading it to 0.14 fixed the issue, but it took a while for > >>> me to realize the need to upgrade so if you're having issues, that might > >>> be > >>> something to consider. > >>> > >>> On Sun, Aug 7, 2022 at 7:56 AM Jason Gerlowski <[email protected]> > >>> wrote: > >>> > >>>> Please vote for release candidate 1 for the Solr Operator v0.6.0 > >>>> > >>>> The artifacts can be downloaded from: > >>>> > >>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.6.0-RC1-rev44b3b5bf03959ff0bf2743fc03d1d7b9e5441f75 > >>>> > >>>> 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.6.0.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.6.0-rc1 > >>>> > >>>> 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.6.0-RC1-rev44b3b5bf03959ff0bf2743fc03d1d7b9e5441f75/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 > >>>> "60392455"); then gpg --export >~/.gnupg/pubring.gpg; fi > >>>> kubectl create -f > >>>> > >>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.6.0-RC1-rev44b3b5bf03959ff0bf2743fc03d1d7b9e5441f75/crds/all-with-dependencies.yaml > >>>> || \ > >>>> kubectl replace -f > >>>> > >>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.6.0-RC1-rev44b3b5bf03959ff0bf2743fc03d1d7b9e5441f75/crds/all-with-dependencies.yaml > >>>> helm install --verify solr-operator apache-solr-rc/solr-operator --set > >>>> image.tag=v0.6.0-rc1 > >>>> helm install --verify example apache-solr-rc/solr > >>>> > >>>> You can run the full smoke tester directly with this command: (First > >>>> checkout the release-0.6 branch of the solr-operator) > >>>> > >>>> ./hack/release/smoke_test/smoke_test.sh -v "v0.6.0" -s "44b3b5b" -i > >>>> "apache/solr-operator:v0.6.0-rc1" -g "60392455" \ > >>>> -l ' > >>>> > >>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.6.0-RC1-rev44b3b5bf03959ff0bf2743fc03d1d7b9e5441f75 > >>>> ' > >>>> > >>>> 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) > >>>> > >>>> ASF policy requires the vote to be open for at least 72 hours i.e. until > >>>> 2022-08-10 15:00 UTC, however since I'm starting this on a weekend, I'll > >>>> be > >>>> sure to keep it open at least through Wednesday Aug 10th. > >>>> > >>>> [ ] +1 approve > >>>> [ ] +0 no opinion > >>>> [ ] -1 disapprove (and reason why) > >>>> > >>>> > >>>> Here is my +1! > >>>> > >>> > >>> > >>> -- > >>> Anshum Gupta > >> > >> --------------------------------------------------------------------- > >> 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]
