Actually let me be the first to vote this down.

-1

I found a bug where VolumeRepository backups are deleted before starting
the next recurring backup, meaning that only 1 backup can be stored at any
given time.

Will submit a (one-line) fix and spin up a new RC later today. (And
hopefully have this use case included in the smoke test as well)

- Houston

On Wed, Nov 10, 2021 at 6:42 PM Houston Putman <hous...@apache.org> wrote:

> Also Tim was very kind and created an 8.11.0 RC1 Solr docker image that
> you can test this out with:
> thelabdude/apache-solr-dev:8.11.0-rc1
>
> And I'll link the draft release notes in case anyone has comments on it:
>
> https://cwiki.apache.org/confluence/display/SOLR/Solr+Operator+Release+Notes+v0.5.0
>
> On Wed, Nov 10, 2021 at 6:39 PM Houston Putman <hous...@apache.org> wrote:
>
>> Please vote for release candidate 1 for the Solr Operator v0.5.0
>>
>> The artifacts can be downloaded from:
>>
>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.0-RC1-rev7d5b4911e7dcadc30a0bfe8173e7dba4af34ad9b
>>
>> 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.0.tgz - Contains the source release
>>   * crds/ - Contains the CRD files
>>   * helm/ - Contains the Helm release packages
>>
>> The RC Docker image can be found at:
>>   apache/solr-operator:v0.5.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.5.0-RC1-rev7d5b4911e7dcadc30a0bfe8173e7dba4af34ad9b/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.0-RC1-rev7d5b4911e7dcadc30a0bfe8173e7dba4af34ad9b/crds/all-with-dependencies.yaml
>> || \
>>     kubectl replace -f
>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.0-RC1-rev7d5b4911e7dcadc30a0bfe8173e7dba4af34ad9b/crds/all-with-dependencies.yaml
>>   helm install --verify solr-operator apache-solr-rc/solr-operator --set
>> image.tag=v0.5.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.5 branch of the solr-operator)
>>
>> ./hack/release/smoke_test/smoke_test.sh -v "v0.5.0" -s "7d5b491" -i
>> "apache/solr-operator:v0.5.0-rc1" -g "98F3F6EC" \
>>     -l '
>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.5.0-RC1-rev7d5b4911e7dcadc30a0bfe8173e7dba4af34ad9b
>> '
>>
>> 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)
>>
>> 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)
>>   - Go 1.16
>>   - 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 2021-11-15 00:00
>> UTC. (Monday since the vote would end on the weekend)
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1
>>
>

Reply via email to