I finally found the missing rule
- verbs:
- '*'
apiGroups:
- solr.apache.org
resources:
- solrclouds/finalizers
I did not specify any action for the moment.
I will create another issue for that
On Thu, Apr 22, 2021 at 5:52 PM Houston Putman <[email protected]>
wrote:
> Yes, please create an issue for that. We can discuss it further there.
>
> On Thu, Apr 22, 2021 at 10:39 AM Thomas Wöckinger <
> [email protected]> wrote:
>
>> Should I create an issue for that?
>>
>> On Thu, Apr 22, 2021 at 5:02 PM Houston Putman <[email protected]>
>> wrote:
>>
>>> Thomas,
>>>
>>> zookeeper-operator:
>>>> crd:
>>>> create: false
>>>> install: false
>>>> use: false
>>>>
>>>> This configuration leads to following error log:
>>>>
>>>> 2021-04-22T10:03:25.816Z ERROR controller-runtime.source if kind is a
>>>> CRD, it should be installed before calling Start {"kind": "
>>>> ZookeeperCluster.zookeeper.pravega.io
>>>> <http://zookeepercluster.zookeeper.pravega.io/>", "error": "no matches
>>>> for kind \"ZookeeperCluster\" in version \"
>>>> zookeeper.pravega.io/v1beta1\ <http://zookeeper.pravega.io/v1beta1%5C>
>>>> ""}
>>>>
>>>
>>> Thanks for testing this out. This is certainly a bug, and one that has
>>> apparently been there for quite a while. It's a good catch and will
>>> certainly require an RC3.
>>>
>>> As for this:
>>>
>>> W0422 10:14:10.474780 1 warnings.go:70] networking.k8s.io/v1beta1
>>> Ingress
>>>> is deprecated in v1.19+, unavailable in v1.22+; use
>>>> networking.k8s.io/v1 Ingress
>>>>
>>>
>>> It's a non-issue and the result of the Solr Operator supporting a range
>>> of Kubernetes versions. We will upgrade the Ingress version at some point
>>> after 1.22 is released and 1.19 is more common.
>>>
>>> Please continue testing (with the zk-operator enabled for now), and make
>>> sure that the rest of your use case works with this candidate. That way
>>> v0.3.0 RC3 will be even more likely to succeed!
>>>
>>> - Houston
>>>
>>> On Thu, Apr 22, 2021 at 5:17 AM Thomas Wöckinger <
>>> [email protected]> wrote:
>>>
>>>> When using all-with-dependencies.yaml the error does not occur, but i
>>>> think it should be not required to install CRDs which should not be used.
>>>>
>>>> Following warning shows up during installation:
>>>>
>>>> W0422 10:14:10.474780 1 warnings.go:70] networking.k8s.io/v1beta1
>>>> Ingress is deprecated in v1.19+, unavailable in v1.22+; use
>>>> networking.k8s.io/v1 Ingress
>>>>
>>>> On Thu, Apr 22, 2021 at 12:11 PM Thomas Wöckinger <
>>>> [email protected]> wrote:
>>>>
>>>>> I forgot to mention that i installed the all.yaml and not
>>>>> all-with-dependencies.yaml from the crds folder
>>>>>
>>>>> On Thu, Apr 22, 2021 at 12:08 PM Thomas Wöckinger <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> I tried to install the operator with disabled zookeeper, because i
>>>>>> want to manage my own
>>>>>>
>>>>>>
>>>>>> zookeeper-operator:
>>>>>> crd:
>>>>>> create: false
>>>>>> install: false
>>>>>> use: false
>>>>>>
>>>>>> This configuration leads to following error log:
>>>>>>
>>>>>> 2021-04-22T10:03:25.816Z ERROR controller-runtime.source if kind is a
>>>>>> CRD, it should be installed before calling Start {"kind": "
>>>>>> ZookeeperCluster.zookeeper.pravega.io", "error": "no matches for
>>>>>> kind \"ZookeeperCluster\" in version \"zookeeper.pravega.io/v1beta1\
>>>>>> <http://zookeeper.pravega.io/v1beta1%5C>""}
>>>>>> github.com/go-logr/zapr.(*zapLogger).Error
>>>>>> /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:132
>>>>>> sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start
>>>>>> /go/pkg/mod/
>>>>>> sigs.k8s.io/[email protected]/pkg/source/source.go:117
>>>>>>
>>>>>> sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1
>>>>>> /go/pkg/mod/
>>>>>> sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:140
>>>>>>
>>>>>> sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start
>>>>>> /go/pkg/mod/
>>>>>> sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:175
>>>>>>
>>>>>> sigs.k8s.io/controller-runtime/pkg/manager.(*controllerManager).startRunnable.func1
>>>>>> /go/pkg/mod/
>>>>>> sigs.k8s.io/[email protected]/pkg/manager/internal.go:661
>>>>>> 2021-04-22T10:03:25.816Z INFO controller Stopping workers
>>>>>> {"reconcilerGroup": "solr.apache.org", "reconcilerKind":
>>>>>> "SolrBackup", "controller": "solrbackup"}
>>>>>> 2021-04-22T10:03:25.816Z INFO controller Stopping workers
>>>>>> {"reconcilerGroup": "solr.apache.org", "reconcilerKind":
>>>>>> "SolrPrometheusExporter", "controller": "solrprometheusexporter"}
>>>>>> 2021-04-22T10:03:25.816Z ERROR controller-runtime.manager error
>>>>>> received after stop sequence was engaged {"error": "context canceled"}
>>>>>> github.com/go-logr/zapr.(*zapLogger).Error
>>>>>> /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:132
>>>>>>
>>>>>> sigs.k8s.io/controller-runtime/pkg/manager.(*controllerManager).engageStopProcedure.func1
>>>>>> /go/pkg/mod/
>>>>>> sigs.k8s.io/[email protected]/pkg/manager/internal.go:521
>>>>>> 2021-04-22T10:03:25.816Z ERROR setup problem running manager
>>>>>> {"error": "no matches for kind \"ZookeeperCluster\" in version \"
>>>>>> zookeeper.pravega.io/v1beta1\
>>>>>> <http://zookeeper.pravega.io/v1beta1%5C>""}
>>>>>> github.com/go-logr/zapr.(*zapLogger).Error
>>>>>> /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:132
>>>>>> main.main
>>>>>> /workspace/main.go:179
>>>>>> runtime.main
>>>>>> /usr/local/go/src/runtime/proc.go:225
>>>>>>
>>>>>> So it seems there is still a CRD or something else required
>>>>>>
>>>>>>
>>>>>> On Thu, Apr 22, 2021 at 10:10 AM Thomas Wöckinger <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Timothy can you provide an example yaml of your cluster, i am
>>>>>>> reading through the CRDs, but i am not sure about BASIC AUTH.
>>>>>>> The description says that two users will be created during
>>>>>>> bootstrap, but where can I find the generated passwords?
>>>>>>>
>>>>>>> Thx for your time!
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Apr 22, 2021 at 1:08 AM Timothy Potter <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 (binding)
>>>>>>>>
>>>>>>>> Ran the smoke tester and deployed a 3-node to GKE with TLS + basic
>>>>>>>> auth + anti-affinity + auto-scaling policy + prom / grafana metrics
>>>>>>>> +
>>>>>>>> zone aware query routing ~ the works!
>>>>>>>>
>>>>>>>> Thank you for the amazing work on this release Houston.
>>>>>>>>
>>>>>>>> On Wed, Apr 21, 2021 at 3:55 PM Houston Putman <[email protected]>
>>>>>>>> wrote:
>>>>>>>> >
>>>>>>>> > Please vote for release candidate 2 for the Solr Operator v0.3.0
>>>>>>>> >
>>>>>>>> > The artifacts can be downloaded from:
>>>>>>>> >
>>>>>>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.3.0-RC2-rev4ec41cb3ebf879b352dc08ae5f789c6ff86b7a04
>>>>>>>> >
>>>>>>>> > 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.3.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.3.0-rc2
>>>>>>>> >
>>>>>>>> > The RC Helm repo can be added with:
>>>>>>>> > helm repo add solr-operator-rc
>>>>>>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.3.0-RC2-rev4ec41cb3ebf879b352dc08ae5f789c6ff86b7a04/helm-charts
>>>>>>>> >
>>>>>>>> > You can install the RC Solr Operator and Solr CRDs 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.3.0-RC2-rev4ec41cb3ebf879b352dc08ae5f789c6ff86b7a04/crds/all-with-dependencies.yaml
>>>>>>>> || \
>>>>>>>> > kubectl replace -f
>>>>>>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.3.0-RC2-rev4ec41cb3ebf879b352dc08ae5f789c6ff86b7a04/crds/all-with-dependencies.yaml
>>>>>>>> > helm install --verify solr-operator
>>>>>>>> solr-operator-rc/solr-operator --set image.tag=v0.3.0-rc2
>>>>>>>> >
>>>>>>>> > You can run the full smoke tester directly with this command:
>>>>>>>> (First checkout the release-0.3 branch of the solr-operator)
>>>>>>>> >
>>>>>>>> > ./hack/release/smoke_test/smoke_test.sh -v "v0.3.0" -s "4ec41cb"
>>>>>>>> -i "apache/solr-operator:v0.3.0-rc2" -g "98F3F6EC" \
>>>>>>>> > -l '
>>>>>>>> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.3.0-RC2-rev4ec41cb3ebf879b352dc08ae5f789c6ff86b7a04
>>>>>>>> '
>>>>>>>> >
>>>>>>>> > 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-04-26
>>>>>>>> 19:00 UTC. (Extended due to the weekend)
>>>>>>>> >
>>>>>>>> > [ ] +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]
>>>>>>>>
>>>>>>>>
