landb-operator issueshttps://gitlab.cern.ch/paas-tools/operators/landb-operator/-/issues2023-01-25T11:15:24+01:00https://gitlab.cern.ch/paas-tools/operators/landb-operator/-/issues/3Add field spec.insertInSets to LanDB sets2023-01-25T11:15:24+01:00Joao Esteves MarcalAdd field spec.insertInSets to LanDB setsThis field will be used to fullfill the issue https://gitlab.cern.ch/webservices/webframeworks-planning/-/issues/65#note_3681671This field will be used to fullfill the issue https://gitlab.cern.ch/webservices/webframeworks-planning/-/issues/65#note_3681671Joao Esteves MarcalJoao Esteves Marcalhttps://gitlab.cern.ch/paas-tools/operators/landb-operator/-/issues/4Improve/introduce ownership to LanDB sets2020-09-28T17:40:59+02:00Joao Esteves MarcalImprove/introduce ownership to LanDB setsCurrently, the only information regarding ownership of LanDB Sets present in a Set is their name that usually follows the convention `IT OKD <clustername> <hint at the set content>` e.g `IT OKD WEBEOS ALL NODES`
the description of the se...Currently, the only information regarding ownership of LanDB Sets present in a Set is their name that usually follows the convention `IT OKD <clustername> <hint at the set content>` e.g `IT OKD WEBEOS ALL NODES`
the description of the set usually also contains the name of the cluster.
My personal suggestion would be to start using the description field for the formated ownership information similar to what we did with the `DelegatedDomains`.
`MANAGED BY landb-operator CLUSTER='{{ cluster_name }}' NAMESPACE='{{ meta.namespace }}' NAME='{{ meta.name }}'`
cc/ @alossent @kolodzieJoao Esteves MarcalJoao Esteves Marcalhttps://gitlab.cern.ch/paas-tools/operators/landb-operator/-/issues/2Document how to manually delete LanDB resources2020-07-30T15:56:42+02:00Alexandre LossentDocument how to manually delete LanDB resourcesAs per https://gitlab.cern.ch/paas-tools/okd4-install/-/merge_requests/157/diffs?diff_id=612850#8ec9a00bfd09b3190ac6b22251dbb1aa95a0579d_219_219 we now create LanDB resources for each cluster including CI and dev clusters.
This means po...As per https://gitlab.cern.ch/paas-tools/okd4-install/-/merge_requests/157/diffs?diff_id=612850#8ec9a00bfd09b3190ac6b22251dbb1aa95a0579d_219_219 we now create LanDB resources for each cluster including CI and dev clusters.
This means possibly these resources may not be cleaned up. (job interrupted, deprovisioning non-functional cluster etc.)
I think we need:
1. implement soap call to list sets/delegated domains so we can find what to clean up
2. complete cleanup instructions in this project's README to find resources to clean up and delete them (e.g. using `oc exec` in a functional cluster so we have all the secrets etc.)
3. add link to the "cleanup" instructions to `ok4-install`'s READMEJoao Esteves MarcalJoao Esteves Marcalhttps://gitlab.cern.ch/paas-tools/operators/landb-operator/-/issues/1Change watch to all namespaces2020-06-22T16:23:20+02:00Joao Esteves MarcalChange watch to all namespaces> Ha, and we will also probably need to watch for all namespaces indeed. Let's make this configurable in the landb-operator Helm chart with a new `watchNamespace` Helm value that gets passed to the deployment's `WATCH_NAMESPACE` (I see n...> Ha, and we will also probably need to watch for all namespaces indeed. Let's make this configurable in the landb-operator Helm chart with a new `watchNamespace` Helm value that gets passed to the deployment's `WATCH_NAMESPACE` (I see no problem to use `""` as default value and watch all namespaces by default)Joao Esteves MarcalJoao Esteves Marcal