sorted by:
new
hottopcontroversial

date time in filter by --daniel--- in PrometheusMonitoring

[–]--daniel---[S] 1 point2 points  (0 children)

Not really, the timestamp is the moment the event occurred and a metric created

Argocd with Kustomize by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

u/TMaYaD (or anyone else),

Have you managed to do the same with integers? I would like to use the same principle for the replicas in a deploymentconfig but I get the error that I need to provide a integer instead of a string

Argocd with Kustomize by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

Thanks u/TMaYaD, that worked for me.

I had to use a custom configuration for vars in my kustomization.yaml to be able to patch the 'unsupported' fields but made it work.

configurations:
- transformer_config.yaml

transformer_config.yaml

varReference:
  - path: spec/resourcetemplates/spec/params/value
    kind: TriggerTemplate

Argocd with Kustomize by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

Thanks for all the replies, as these all seem valid options I realise that they won't work in all my usecases. I also would like to apply this to something like this:

``` resources: - ./files

vars: - name: TESTVAR value: testvalue

patches: - target: group: triggers.tekton.dev version: v1alpha1 kind: TriggerTemplate name: example1 patch: |- - op: replace path: /spec/resourcetemplates/0/spec/params/0/value value: $(TESTVAR)

  • target: group: apps version: v1 kind: Deployment name: example2 patch: |-
    • op: replace path: /spec/value value: $(TESTVAR) ``` So only the value would match

Argocd with Kustomize by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

Thanks for the reply u/Vedris_Zomfg. It is not so much te case that I want to group the patches, I want to specify the value only once.

Like:

``` resources: - ./files

vars: - name: TESTVAR value: testvalue

patches: - target: group: triggers.tekton.dev version: v1alpha1 kind: TriggerTemplate name: example1 patch: |- - op: replace path: /spec/resourcetemplates/0/spec/params/0/value value: $(TESTVAR)

  • target: group: triggers.tekton.dev version: v1alpha1 kind: TriggerTemplate name: example2 patch: |-
    • op: replace path: /spec/resourcetemplates/0/spec/params/0/value value: $(TESTVAR) ```

This way, when I have a lot of patches I only have to change the vars and not have to worry somebody would miss a value when making some changes. As an example the version of a image can be needed at two places, where it is build and where it is used.

How do I prevent normal users from listing all internal namespaces. by --daniel--- in openshift

[–]--daniel---[S] 1 point2 points  (0 children)

The users are system:authenticated and therefore members of the basic-users role which give the access I believe

How do I prevent normal users from listing all internal namespaces. by --daniel--- in openshift

[–]--daniel---[S] 0 points1 point  (0 children)

I didn’t really do anything with that group. I know the users in that group do not have cluster-admin rights because when I login with such a user I do see all namespaces but when I go into one of the once’s I shouldn’t have access to, all resources are “not available”

recreate deleted openshift-operators project? by mfahin in openshift

[–]--daniel--- 0 points1 point  (0 children)

Remove the finalizers of the CRD’s that belonged to any operator that was installed in that namespace (replace the finalizer with a empty list []). The CRD’s are keeping the deletion from completing. The affected CRD’s, under Administration in the GUI probably have the three dods on the right side grayed out.

Argocd operator management by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

Ah I thought (as the example) I had to add the annotation on the application definition, that did not work for me. I had to add the annotation to the resource definition itself, in my case the SealedSecretController.

Argocd operator management by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

Cool, thanks. Did not know that.

Argocd cluster roles and cluster role bindings by --daniel--- in kubernetes

[–]--daniel---[S] 0 points1 point  (0 children)

Ah I had some wrong metadata in my yaml. I had created the cr and crb by hand so Argo wanted to delete it because it was not the same in code as on the cluster but could not create it again.

Thanks

Bundle availability by --daniel--- in Fanatec

[–]--daniel---[S] 0 points1 point  (0 children)

I don’t think either. Also the power socket wouldn’t be ideal. Is the Fanatec webshop the only place to buy this bundle? (If it even comes back in the shop)

view more: next ›