| // a program to sort keys in a given directory with yaml files | |
| package main | |
| import ( | |
| "fmt" | |
| "io/ioutil" | |
| "log" | |
| "os" | |
| "sort" | |
| "strings" |
| apiVersion: apiextensions.crossplane.io/v1 | |
| kind: Composition | |
| metadata: | |
| annotations: | |
| name: vcluster.caas.telekom.de | |
| spec: | |
| compositeTypeRef: | |
| apiVersion: caas.telekom.de/v1alpha1 | |
| kind: Vcluster | |
| mode: Resources |
| # adjust s3 access_key,host_base, secret_key, and s3 bucketname | |
| apiVersion: v1 | |
| kind: Secret | |
| metadata: | |
| name: s3cfg | |
| type: Opaque | |
| stringData: | |
| .s3cfg: |- | |
| [default] | |
| access_key = xxxxx |
| package mystruct | |
| // LoggingSpec defines the desired state of Logging | |
| type MyStruct struct { | |
| // Reference to the logging system. Each of the `loggingRef`s can manage a fluentbit daemonset and a fluentd statefulset. | |
| LoggingRef string `json:"loggingRef,omitempty"` | |
| // Disable configuration check before applying new fluentd configuration. | |
| FlowConfigCheckDisabled bool `json:"flowConfigCheckDisabled,omitempty"` | |
| // Whether to skip invalid Flow and ClusterFlow resources |
| --- | |
| apiVersion: v1 | |
| kind: ServiceAccount | |
| metadata: | |
| labels: | |
| name: getpods | |
| name: getpods | |
| --- | |
| apiVersion: rbac.authorization.k8s.io/v1 | |
| kind: Role |
| --- | |
| apiVersion: apps/v1 | |
| kind: StatefulSet | |
| metadata: | |
| labels: | |
| app: curl-client | |
| name: curl-client | |
| spec: | |
| serviceName: curl-client | |
| replicas: 1 |
| #!/bin/sh | |
| # keycloak saml user object: | |
| # principalIds: | |
| # - keycloak_user://[email protected] | |
| # - local://u-pxxxxxxx | |
| # | |
| # keycloak oidc user object: | |
| # principalIds: | |
| # - keycloakoidc_user://[email protected] |
| # Copyright 2017 The Kubernetes Authors. | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 | |
| # | |
| # Unless required by applicable law or agreed to in writing, software | |
| # distributed under the License is distributed on an "AS IS" BASIS, |
| # This behaviour comes in Kubernetes 1.21 with a change of Serviceaccount token format. Bound tokens become default, legacy | |
| # token still alive. In prometheus-auth, a middleware | |
| # for bearer token auth in front of prometheus, a SubjectAccessReview will looking for a token, provided by the federated | |
| # prometheus instance via http endpoint. This token is searched in a list of secrets cluster-wide and if there is a match, | |
| # comparing process started for ServiceAccount and Namespace. After success, a hijack federate will provide access to the | |
| # related cluster metrics. Normaly, the token in the federate call and the content of the related secret of the | |
| # ServiceAccount is equal. In newer Kubernetes version this format is rewritten and internally the new format of bound token | |
| # is stored. | |
| ä With this difference, the SubjectAccessReview is denied and no metrics are accessable. Unfortunatelly the related | |
| # ServiceMonitor for federate is UP, no errors are visiable. |