From 4976674b33e91e37569a3d4d47be6c27c273755d Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 19 Aug 2026 16:08:43 +0000 Subject: [PATCH 1/6] Replace prometheus with pickle --- __tests__/crawler.test.js | 6 +- .../urls_projectcalico.docs.tigera.io.txt | 6 +- __tests__/data/urls_with_canonicals.txt | 126 ++-- .../components/FelixConfig/config-params.json | 30 +- .../get-started/operator-checklist.mdx | 16 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../mark-lb-node-for-maintenance.mdx | 2 +- calico-cloud/operations/comms/index.mdx | 8 +- calico-cloud/operations/disconnect.mdx | 2 +- calico-cloud/operations/index.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 8 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 92 +-- .../prometheus/configure-prometheus.mdx | 80 +-- .../operations/monitor/prometheus/support.mdx | 6 +- calico-cloud/reference/attribution.mdx | 4 +- .../kube-controllers/index.mdx | 2 +- calico-cloud/reference/index.mdx | 4 +- calico-cloud/reference/installation/_api.mdx | 36 +- .../resources/kubecontrollersconfig.mdx | 4 +- calico-cloud/releases.json | 20 +- calico-cloud/threat/configuring-webhooks.mdx | 2 +- .../components/FelixConfig/config-params.json | 28 +- .../get-started/operator-checklist.mdx | 16 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../operations/comms/secure-metrics.mdx | 76 +- .../version-22-2/operations/disconnect.mdx | 2 +- .../version-22-2/operations/index.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 8 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 90 +-- .../prometheus/configure-prometheus.mdx | 84 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../version-22-2/reference/attribution.mdx | 4 +- .../kube-controllers/index.mdx | 2 +- .../version-22-2/reference/index.mdx | 4 +- .../reference/installation/_api.mdx | 36 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-22-2/releases.json | 40 +- .../threat/configuring-webhooks.mdx | 2 +- .../components/FelixConfig/config-params.json | 30 +- .../get-started/operator-checklist.mdx | 16 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../mark-lb-node-for-maintenance.mdx | 2 +- .../version-23-2/operations/comms/index.mdx | 8 +- .../version-23-2/operations/disconnect.mdx | 2 +- .../version-23-2/operations/index.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 8 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 92 +-- .../prometheus/configure-prometheus.mdx | 80 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../version-23-2/reference/attribution.mdx | 4 +- .../kube-controllers/index.mdx | 2 +- .../version-23-2/reference/index.mdx | 4 +- .../reference/installation/_api.mdx | 36 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-23-2/releases.json | 20 +- .../threat/configuring-webhooks.mdx | 2 +- .../version-22-2-sidebars.json | 14 +- .../version-23-2-sidebars.json | 14 +- .../components/FelixConfig/config-params.json | 30 +- ...gStartedInstallOnClustersKubernetesHelm.js | 8 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 8 +- .../components/PrivateRegistryImagePath.js | 6 +- .../components/PrivateRegistryRegular.js | 6 +- .../components/UpgradeOperatorSimple.js | 4 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../install-on-clusters/kubernetes/helm.mdx | 4 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../getting-started/manifest-archive.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 8 +- .../kubernetes-upgrade-tsee/helm.mdx | 8 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../create-a-managed-cluster-helm.mdx | 4 +- .../create-a-management-cluster-helm.mdx | 8 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../mark-lb-node-for-maintenance.mdx | 2 +- .../review-unused-network-policies.mdx | 4 +- calico-enterprise/operations/comms/index.mdx | 10 +- calico-enterprise/operations/index.mdx | 8 +- .../operations/license-options.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 20 +- .../monitor/metrics/operator-metrics.mdx | 8 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 102 +-- .../prometheus/configure-prometheus.mdx | 80 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../reference/architecture/overview.mdx | 6 +- .../clis/calicoctl/cluster/diags.mdx | 10 +- .../reference/clis/calicoq/host.mdx | 4 +- .../configure-resources.mdx | 12 +- .../kube-controllers/index.mdx | 2 +- .../reference/installation/_api.mdx | 38 +- .../resources/kubecontrollersconfig.mdx | 4 +- calico-enterprise/releases.json | 18 +- .../threat/configuring-webhooks.mdx | 2 +- ...gStartedInstallOnClustersKubernetesHelm.js | 8 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 8 +- .../components/PrivateRegistryImagePath.js | 6 +- .../components/PrivateRegistryRegular.js | 6 +- .../components/UpgradeOperatorSimple.js | 4 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../install-on-clusters/kubernetes/helm.mdx | 4 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../getting-started/manifest-archive.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 6 +- .../kubernetes-upgrade-tsee/helm.mdx | 6 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../create-a-managed-cluster-helm.mdx | 4 +- .../create-a-management-cluster-helm.mdx | 8 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../operations/comms/secure-metrics.mdx | 76 +- .../version-3.20-2/operations/index.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 20 +- .../monitor/metrics/license-agent.mdx | 12 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 90 +-- .../prometheus/configure-prometheus.mdx | 84 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../reference/architecture/overview.mdx | 6 +- .../clis/calicoctl/cluster/diags.mdx | 10 +- .../reference/clis/calicoq/host.mdx | 4 +- .../configure-resources.mdx | 12 +- .../reference/installation/_api.mdx | 36 +- .../reference/resources/felixconfig.mdx | 14 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.20-2/release-notes/index.mdx | 2 +- .../version-3.20-2/releases.json | 200 +++--- .../components/FelixConfig/config-params.json | 28 +- ...gStartedInstallOnClustersKubernetesHelm.js | 8 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 8 +- .../components/PrivateRegistryImagePath.js | 6 +- .../components/PrivateRegistryRegular.js | 6 +- .../components/UpgradeOperatorSimple.js | 4 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../install-on-clusters/kubernetes/helm.mdx | 4 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../getting-started/manifest-archive.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 6 +- .../kubernetes-upgrade-tsee/helm.mdx | 6 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../create-a-managed-cluster-helm.mdx | 4 +- .../create-a-management-cluster-helm.mdx | 8 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../operations/comms/secure-metrics.mdx | 76 +- .../version-3.21-2/operations/index.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 20 +- .../monitor/metrics/license-agent.mdx | 12 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 90 +-- .../prometheus/configure-prometheus.mdx | 84 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../reference/architecture/overview.mdx | 6 +- .../clis/calicoctl/cluster/diags.mdx | 10 +- .../reference/clis/calicoq/host.mdx | 4 +- .../configure-resources.mdx | 12 +- .../reference/installation/_api.mdx | 36 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.21-2/release-notes/index.mdx | 6 +- .../version-3.21-2/releases.json | 220 +++--- .../threat/configuring-webhooks.mdx | 2 +- .../components/FelixConfig/config-params.json | 28 +- ...gStartedInstallOnClustersKubernetesHelm.js | 8 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 8 +- .../components/PrivateRegistryImagePath.js | 6 +- .../components/PrivateRegistryRegular.js | 6 +- .../components/UpgradeOperatorSimple.js | 4 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../install-on-clusters/kubernetes/helm.mdx | 4 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../getting-started/manifest-archive.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 6 +- .../kubernetes-upgrade-tsee/helm.mdx | 6 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../create-a-managed-cluster-helm.mdx | 4 +- .../create-a-management-cluster-helm.mdx | 8 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../operations/comms/secure-metrics.mdx | 76 +- .../version-3.22-2/operations/index.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 20 +- .../monitor/metrics/license-agent.mdx | 12 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 90 +-- .../prometheus/configure-prometheus.mdx | 84 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../reference/architecture/overview.mdx | 6 +- .../clis/calicoctl/cluster/diags.mdx | 10 +- .../reference/clis/calicoq/host.mdx | 4 +- .../configure-resources.mdx | 12 +- .../reference/installation/_api.mdx | 36 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.22-2/release-notes/index.mdx | 4 +- .../version-3.22-2/releases.json | 180 ++--- .../threat/configuring-webhooks.mdx | 2 +- .../components/FelixConfig/config-params.json | 30 +- ...gStartedInstallOnClustersKubernetesHelm.js | 8 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 8 +- .../components/PrivateRegistryImagePath.js | 6 +- .../components/PrivateRegistryRegular.js | 6 +- .../components/UpgradeOperatorSimple.js | 4 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../install-on-clusters/kubernetes/helm.mdx | 4 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../getting-started/manifest-archive.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 6 +- .../kubernetes-upgrade-tsee/helm.mdx | 6 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../create-a-managed-cluster-helm.mdx | 4 +- .../create-a-management-cluster-helm.mdx | 8 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../mark-lb-node-for-maintenance.mdx | 2 +- .../review-unused-network-policies.mdx | 4 +- .../version-3.23-2/operations/comms/index.mdx | 10 +- .../version-3.23-2/operations/index.mdx | 8 +- .../operations/license-options.mdx | 6 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 20 +- .../monitor/metrics/license-agent.mdx | 12 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 90 +-- .../prometheus/configure-prometheus.mdx | 80 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../reference/architecture/overview.mdx | 6 +- .../clis/calicoctl/cluster/diags.mdx | 10 +- .../reference/clis/calicoq/host.mdx | 4 +- .../configure-resources.mdx | 12 +- .../kube-controllers/index.mdx | 2 +- .../reference/installation/_api.mdx | 36 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.23-2/releases.json | 60 +- .../threat/configuring-webhooks.mdx | 2 +- .../components/FelixConfig/config-params.json | 30 +- ...gStartedInstallOnClustersKubernetesHelm.js | 8 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 8 +- .../components/PrivateRegistryImagePath.js | 6 +- .../components/PrivateRegistryRegular.js | 6 +- .../components/UpgradeOperatorSimple.js | 4 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../install-on-clusters/kubernetes/helm.mdx | 4 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../getting-started/manifest-archive.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 8 +- .../kubernetes-upgrade-tsee/helm.mdx | 8 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../create-a-managed-cluster-helm.mdx | 4 +- .../create-a-management-cluster-helm.mdx | 8 +- .../beginners/simple-policy-cnx.mdx | 14 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../mark-lb-node-for-maintenance.mdx | 2 +- .../review-unused-network-policies.mdx | 4 +- .../version-3.24-1/operations/comms/index.mdx | 10 +- .../version-3.24-1/operations/index.mdx | 8 +- .../operations/license-options.mdx | 8 +- .../monitor/metrics/bgp-metrics.mdx | 10 +- .../elasticsearch-and-fluentd-metrics.mdx | 20 +- .../monitor/metrics/operator-metrics.mdx | 8 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/alertmanager.mdx | 8 +- .../monitor/prometheus/byo-prometheus.mdx | 102 +-- .../prometheus/configure-prometheus.mdx | 80 +-- .../operations/monitor/prometheus/support.mdx | 6 +- .../reference/architecture/overview.mdx | 6 +- .../clis/calicoctl/cluster/diags.mdx | 10 +- .../reference/clis/calicoq/host.mdx | 4 +- .../configure-resources.mdx | 12 +- .../kube-controllers/index.mdx | 2 +- .../reference/installation/_api.mdx | 38 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.24-1/releases.json | 16 +- .../threat/configuring-webhooks.mdx | 2 +- .../version-3.20-2-sidebars.json | 16 +- .../version-3.21-2-sidebars.json | 16 +- .../version-3.22-2-sidebars.json | 16 +- .../version-3.23-2-sidebars.json | 16 +- .../version-3.24-1-sidebars.json | 16 +- .../components/FelixConfig/config-params.json | 20 +- .../network-policy/comms/secure-metrics.mdx | 76 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 76 +- .../monitor/monitor-component-visual.mdx | 18 +- calico/reference/calicoctl/cluster/diags.mdx | 10 +- calico/reference/index.mdx | 4 +- calico/reference/installation/_api.mdx | 8 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../components/FelixConfig/config-params.json | 12 +- .../network-policy/comms/secure-metrics.mdx | 76 +- .../monitor/monitor-component-metrics.mdx | 76 +- .../monitor/monitor-component-visual.mdx | 18 +- .../version-3.29/reference/index.mdx | 4 +- .../reference/installation/_api.mdx | 8 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.29/release-notes/index.mdx | 2 +- .../components/FelixConfig/config-params.json | 12 +- .../network-policy/comms/secure-metrics.mdx | 76 +- .../monitor/monitor-component-metrics.mdx | 76 +- .../monitor/monitor-component-visual.mdx | 18 +- .../reference/calicoctl/cluster/diags.mdx | 10 +- .../version-3.30/reference/index.mdx | 4 +- .../reference/installation/_api.mdx | 8 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../components/FelixConfig/config-params.json | 12 +- .../network-policy/comms/secure-metrics.mdx | 76 +- .../monitor/monitor-component-metrics.mdx | 76 +- .../monitor/monitor-component-visual.mdx | 18 +- .../reference/calicoctl/cluster/diags.mdx | 10 +- .../version-3.31/reference/index.mdx | 4 +- .../reference/installation/_api.mdx | 8 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../components/FelixConfig/config-params.json | 20 +- .../network-policy/comms/secure-metrics.mdx | 76 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 76 +- .../monitor/monitor-component-visual.mdx | 18 +- .../reference/calicoctl/cluster/diags.mdx | 10 +- .../version-3.32/reference/index.mdx | 4 +- .../reference/installation/_api.mdx | 8 +- .../resources/kubecontrollersconfig.mdx | 4 +- .../version-3.32/release-notes/index.mdx | 2 +- .../version-3.29-sidebars.json | 6 +- .../version-3.30-sidebars.json | 6 +- .../version-3.31-sidebars.json | 6 +- .../version-3.32-sidebars.json | 6 +- scripts/versions/main.go | 2 +- sidebars-calico-cloud.js | 14 +- sidebars-calico-enterprise.js | 16 +- sidebars-calico.js | 6 +- src/___new___/data/ccImageLists.js | 104 +-- src/utils/linkChecker.js | 2 +- static/_headers | 4 +- static/_redirects | 8 +- static/calico-cloud/llms-full.txt | 414 +++++------ static/calico-cloud/llms.txt | 14 +- static/calico-enterprise/llms-full.txt | 664 +++++++++--------- static/calico-enterprise/llms.txt | 16 +- .../licenses/third-party-attributions.html | 12 +- static/calico/3.26/licenses/index.html | 12 +- .../licenses/third-party-attributions.html | 32 +- .../licenses/third-party-attributions.html | 32 +- .../licenses/third-party-attributions.html | 32 +- .../licenses/third-party-attributions.html | 32 +- .../licenses/third-party-attributions.html | 60 +- .../licenses/third-party-attributions.html | 40 +- static/calico/llms-full.txt | 268 +++---- static/calico/llms.txt | 6 +- static/files/min-ui-user-rbac.yaml | 2 +- static/files/read-all-crud-default-rbac.yaml | 2 +- static/json/calico-api-swagger.json | 2 +- 403 files changed, 3973 insertions(+), 3973 deletions(-) diff --git a/__tests__/crawler.test.js b/__tests__/crawler.test.js index 8f59cc2d4b..916daac095 100644 --- a/__tests__/crawler.test.js +++ b/__tests__/crawler.test.js @@ -135,7 +135,7 @@ test('Crawl the docs and execute tests', async () => { 'https://tools.ietf.org/html/rfc1123', 'http://cr.yp.to/libtai/tai64.html#tai64n', 'https://thenewstack.io/faster-troubleshooting-with-dynamic-packet-capture/', //==>Origin: http://localhost:4242/calico-cloud/visibility/packetcapture - 'https://golang.org/pkg/crypto/tls/#ClientAuthType', //==>Origin: https://downloads.tigera.io/ee/v3.17.0/manifests/tigera-prometheus-operator.yaml. The dead link is automatically redirected to a working page, so no fix needed in the origin. + 'https://golang.org/pkg/crypto/tls/#ClientAuthType', //==>Origin: https://downloads.tigera.io/ee/v3.17.0/manifests/tigera-pickle-operator.yaml. The dead link is automatically redirected to a working page, so no fix needed in the origin. 'https://downloads.tigera.io/ee/archives/release-master-master.tgz', //==> This started after redesigning the archive procedure. 'http://nginx-svc.curl-ns.svc.cluster.local:80', 'http://nginx-svc.service-ns.svc.cluster.local:80', @@ -188,8 +188,8 @@ test('Crawl the docs and execute tests', async () => { 'https://www.tigera.io/blog/why-bgp/', 'https://docs.nginx.com/nginx-ingress-controller/configuration/', 'https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource', - 'https://prometheus.io/docs/prometheus/latest/disabled_features/', // ==>Origin: https://downloads.tigera.io/ee/v3.17.4/manifests/tigera-prometheus-operator.yaml - 'https://prometheus.io/docs/prometheus/latest/feature_flags/', // ==>Origin: https://downloads.tigera.io/ee/v3.20.0-1.0/manifests/tigera-prometheus-operator.yaml + 'https://pickle.io/docs/pickle/latest/disabled_features/', // ==>Origin: https://downloads.tigera.io/ee/v3.17.4/manifests/tigera-pickle-operator.yaml + 'https://pickle.io/docs/pickle/latest/feature_flags/', // ==>Origin: https://downloads.tigera.io/ee/v3.20.0-1.0/manifests/tigera-pickle-operator.yaml 'https://docs.fluentd.org/filter/grep', 'https://techcommunity.microsoft.com/t5/networking-blog/direct-server-return-dsr-in-a-nutshell/ba-p/693710', 'https://www.f5.com/glossary/cookie-poisoning', //TEMPORARY diff --git a/__tests__/data/urls_projectcalico.docs.tigera.io.txt b/__tests__/data/urls_projectcalico.docs.tigera.io.txt index c0fd839b11..c1b850a005 100644 --- a/__tests__/data/urls_projectcalico.docs.tigera.io.txt +++ b/__tests__/data/urls_projectcalico.docs.tigera.io.txt @@ -142,7 +142,7 @@ https://projectcalico.docs.tigera.io/getting-started/kubernetes/self-managed-pub https://projectcalico.docs.tigera.io/getting-started/openstack/installation/redhat https://projectcalico.docs.tigera.io/security/http-methods https://projectcalico.docs.tigera.io/reference/vpp/host-network -https://projectcalico.docs.tigera.io/reference/felix/prometheus +https://projectcalico.docs.tigera.io/reference/felix/pickle https://projectcalico.docs.tigera.io/getting-started/kubernetes/hardway/ https://projectcalico.docs.tigera.io/reference/public-cloud/aws https://projectcalico.docs.tigera.io/getting-started/kubernetes/flannel/ @@ -222,8 +222,8 @@ https://projectcalico.docs.tigera.io/getting-started/bare-metal/about https://projectcalico.docs.tigera.io/reference/calicoctl/overview https://projectcalico.docs.tigera.io/reference/etcd-rbac/certificate-generation https://projectcalico.docs.tigera.io/getting-started/bare-metal/installation/binary-mgr -https://projectcalico.docs.tigera.io/reference/kube-controllers/prometheus -https://projectcalico.docs.tigera.io/reference/typha/prometheus +https://projectcalico.docs.tigera.io/reference/kube-controllers/pickle +https://projectcalico.docs.tigera.io/reference/typha/pickle https://projectcalico.docs.tigera.io/reference/architecture/design/l2-interconnect-fabric https://projectcalico.docs.tigera.io/reference/calicoctl/node/ https://projectcalico.docs.tigera.io/maintenance/clis/calicoctl/install#install-calicoctl-as-a-binary-on-a-single-host diff --git a/__tests__/data/urls_with_canonicals.txt b/__tests__/data/urls_with_canonicals.txt index f8d03eb342..c3b9c5aaff 100644 --- a/__tests__/data/urls_with_canonicals.txt +++ b/__tests__/data/urls_with_canonicals.txt @@ -20,7 +20,7 @@ https://docs.tigera.io/v3.8/about/about-calico-enterprise/ https://docs.tigera.io/v3.12/security/aws-integration/aws-security-group-integration https://docs.tigera.io/v3.11/release-notes/ https://docs.tigera.io/v3.9/getting-started/bare-metal/installation/container -https://docs.tigera.io/v3.7/reference/felix/prometheus +https://docs.tigera.io/v3.7/reference/felix/pickle https://docs.tigera.io/v3.7/maintenance/performance/ https://docs.tigera.io/v3.7/compliance/compliance-reports/overview https://docs.tigera.io/v3.7/networking/ @@ -93,7 +93,7 @@ https://docs.tigera.io/v3.7/reference/resources/hostendpoint https://docs.tigera.io/v3.7/getting-started/bare-metal/installation/binary https://docs.tigera.io/v3.7/networking/ipv6 https://docs.tigera.io/v3.0/getting-started/ -https://docs.tigera.io/v3.0/maintenance/monitor/prometheus +https://docs.tigera.io/v3.0/maintenance/monitor/pickle https://docs.tigera.io/v3.7/reference/resources/workloadendpoint https://docs.tigera.io/v3.0/security/logs/elastic/dns https://docs.tigera.io/v3.7/getting-started/kubernetes/requirements @@ -293,7 +293,7 @@ https://docs.tigera.io/v3.7/getting-started/cnx/roles-and-permissions https://docs.tigera.io/v3.7/security/aws-integration/tiers-and-policy https://docs.tigera.io/v3.7/reference/calicoctl/create https://docs.tigera.io/v3.7/maintenance/troubleshoot/component-logs -https://docs.tigera.io/v3.7/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.7/reference/kube-controllers/pickle https://docs.tigera.io/v3.7/reference/resources/networkpolicy https://docs.tigera.io/v3.7/multicluster/federation/aws https://docs.tigera.io/v3.7/visibility/iptables @@ -303,13 +303,13 @@ https://docs.tigera.io/v3.0/reference/typha/configuration https://docs.tigera.io/v3.0/reference/resources/networkpolicy https://docs.tigera.io/v3.0/reference/resources/profile https://docs.tigera.io/v3.0/reference/calicoctl/create -https://docs.tigera.io/v3.7/maintenance/monitor/prometheus +https://docs.tigera.io/v3.7/maintenance/monitor/pickle https://docs.tigera.io/v3.7/security/tutorials/kubernetes-policy-basic https://docs.tigera.io/v3.0/getting-started/bare-metal/installation/container https://docs.tigera.io/v3.7/reference/cni-plugin/configuration https://docs.tigera.io/v3.0/reference/felix/ https://docs.tigera.io/v3.7/reference/host-endpoints/pre-dnat -https://docs.tigera.io/v3.0/reference/felix/prometheus +https://docs.tigera.io/v3.0/reference/felix/pickle https://docs.tigera.io/v3.7/reference/calicoq/overview https://docs.tigera.io/v3.7/networking/mtu https://docs.tigera.io/v3.0/security/tutorials/protect-hosts @@ -625,7 +625,7 @@ https://docs.tigera.io/v3.11/multicluster/federation/ https://docs.tigera.io/v3.13/threat/web-application-firewall https://docs.tigera.io/v3.13/security/tutorials/kubernetes-policy-basic https://docs.tigera.io/v3.11/reference/attribution/attribution -https://docs.tigera.io/v3.6/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.6/reference/kube-controllers/pickle https://docs.tigera.io/v3.6/threat/honeypod/honeypod-controller https://docs.tigera.io/v3.1/reference/calicoctl/node/diags https://docs.tigera.io/v2.7/reference/public-cloud/ @@ -761,7 +761,7 @@ https://docs.tigera.io/v3.3/reference/calicoctl/ipam/show https://docs.tigera.io/v3.1/reference/ https://docs.tigera.io/v3.9/reference/resources/remoteclusterconfiguration https://docs.tigera.io/v3.6/reference/calicoctl/label -https://docs.tigera.io/v3.9/reference/felix/prometheus +https://docs.tigera.io/v3.9/reference/felix/pickle https://docs.tigera.io/v2.7/security/comms/crypto-auth https://docs.tigera.io/v3.13/maintenance/clis/calicoctl/configure/ https://docs.tigera.io/v2.7/reference/architecture/design/l2-interconnect-fabric @@ -793,7 +793,7 @@ https://docs.tigera.io/v3.12/getting-started/calico-enterprise https://docs.tigera.io/v3.12/getting-started/cnx/roles-and-permissions https://docs.tigera.io/v3.9/reference/calicoctl/captured-packets https://docs.tigera.io/v3.9/security/policy-firewalls/ -https://docs.tigera.io/v3.3/maintenance/monitor/prometheus +https://docs.tigera.io/v3.3/maintenance/monitor/pickle https://docs.tigera.io/v3.13/reference/calicoctl/delete https://docs.tigera.io/v3.2/networking/ https://docs.tigera.io/v3.12/reference/calicoq/selectors @@ -830,7 +830,7 @@ https://docs.tigera.io/v3.5/threat/anomaly-detection/customizing https://docs.tigera.io/v3.11/getting-started/windows-calico/ https://docs.tigera.io/v3.4/maintenance/upgrading-calico-to-calico-enterprise https://docs.tigera.io/v3.9/networking/ipv6-control-plane -https://docs.tigera.io/v3.9/maintenance/monitor/prometheus/prometheus +https://docs.tigera.io/v3.9/maintenance/monitor/pickle/pickle https://docs.tigera.io/v3.13/reference/resources/globalnetworkset https://docs.tigera.io/v3.9/security/fortinet-integration/overview https://docs.tigera.io/v3.2/reference/public-cloud/gce @@ -844,13 +844,13 @@ https://docs.tigera.io/v3.13/getting-started/kubernetes/quickstart https://docs.tigera.io/v3.13/reference/calicoctl/ipam/show https://docs.tigera.io/v3.9/reference/calicoctl/node/status https://docs.tigera.io/v3.4/getting-started/windows-calico/limitations -https://docs.tigera.io/v3.5/maintenance/monitor/prometheus +https://docs.tigera.io/v3.5/maintenance/monitor/pickle https://docs.tigera.io/v2.7/reference/host-endpoints/forwarded https://docs.tigera.io/v3.9/maintenance/logstorage/ https://docs.tigera.io/v2.8/reference/resources/licensekey https://docs.tigera.io/v3.2/security/simple-policy-cnx -https://docs.tigera.io/v3.13/reference/felix/prometheus -https://docs.tigera.io/v3.4/maintenance/monitor/prometheus +https://docs.tigera.io/v3.13/reference/felix/pickle +https://docs.tigera.io/v3.4/maintenance/monitor/pickle https://docs.tigera.io/v3.13/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.5/getting-started/cnx/access-the-manager https://docs.tigera.io/v3.13/networking/vxlan-ipip @@ -861,7 +861,7 @@ https://docs.tigera.io/v3.1/reference/resources/workloadendpoint https://docs.tigera.io/v3.11/security/panorama-integration/tigera-panorama-address-groups https://docs.tigera.io/v3.5/maintenance/performance/ebpf/ https://docs.tigera.io/v3.3/getting-started/bare-metal/about -https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/alertmanager +https://docs.tigera.io/v3.13/maintenance/monitor/pickle/alertmanager https://docs.tigera.io/v3.9/visibility/elastic/flow/datatypes https://docs.tigera.io/v3.13/policy/ https://docs.tigera.io/v3.12/getting-started/openshift/requirements @@ -957,7 +957,7 @@ https://docs.tigera.io/v3.6/getting-started/bare-metal/installation/ https://docs.tigera.io/v3.2/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.9/getting-started/kubernetes/gke https://docs.tigera.io/v3.13/reference/calicoq/endpoint -https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/prometheus +https://docs.tigera.io/v3.13/maintenance/monitor/pickle/pickle https://docs.tigera.io/v3.2/reference/host-endpoints/summary https://docs.tigera.io/v3.11/security/fortinet-integration/firewall-integration https://docs.tigera.io/v3.9/threat/tor-vpn-feed-and-dashboard @@ -973,7 +973,7 @@ https://docs.tigera.io/v3.6/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/v3.12/compliance/compliance-reports-cis https://docs.tigera.io/v3.2/reference/calicoctl/patch https://docs.tigera.io/v3.3/reference/calicoctl/convert -https://docs.tigera.io/v2.7/reference/felix/prometheus +https://docs.tigera.io/v2.7/reference/felix/pickle https://docs.tigera.io/v3.12/networking/custom-bgp-config https://docs.tigera.io/v3.6/networking/workloads-outside-cluster https://docs.tigera.io/v3.11/reference/host-endpoints/summary @@ -1029,13 +1029,13 @@ https://docs.tigera.io/v3.13/security/default-deny https://docs.tigera.io/v3.13/getting-started/windows-calico/troubleshoot https://docs.tigera.io/v3.6/threat/ingress https://docs.tigera.io/v3.13/maintenance/logstorage/log-storage-recommendations -https://docs.tigera.io/v3.5/reference/felix/prometheus +https://docs.tigera.io/v3.5/reference/felix/pickle https://docs.tigera.io/v3.1/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/v3.6/multicluster/ https://docs.tigera.io/v3.13/security/external-ips-policy https://docs.tigera.io/v3.13/threat/honeypod/honeypod-controller https://docs.tigera.io/v3.5/multicluster/federation/ -https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/alertmanager +https://docs.tigera.io/v3.12/maintenance/monitor/pickle/alertmanager https://docs.tigera.io/v3.6/getting-started/private-registry/private-registry-image-path https://docs.tigera.io/v3.13/security/fortinet-integration/overview https://docs.tigera.io/v3.9/threat/anomaly-detection/overview @@ -1149,7 +1149,7 @@ https://docs.tigera.io/v3.6/getting-started/openshift/ https://docs.tigera.io/v3.12/reference/host-endpoints/failsafe https://docs.tigera.io/v2.7/reference/calicoq/overview https://docs.tigera.io/v3.9/visibility/alerts -https://docs.tigera.io/v3.11/maintenance/monitor/prometheus/alertmanager +https://docs.tigera.io/v3.11/maintenance/monitor/pickle/alertmanager https://docs.tigera.io/v3.3/reference/resources/managedcluster https://docs.tigera.io/v3.4/reference/calicoctl/replace https://docs.tigera.io/v3.13/security/policy-firewalls/ @@ -1321,7 +1321,7 @@ https://docs.tigera.io/v3.9/reference/cni-plugin/configuration https://docs.tigera.io/v2.8/networking/assign-ip-addresses-topology https://docs.tigera.io/v3.12/networking/ipv6 https://docs.tigera.io/v3.9/getting-started/install-on-clusters/ -https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/byo-prometheus +https://docs.tigera.io/v3.12/maintenance/monitor/pickle/byo-pickle https://docs.tigera.io/v3.9/visibility/elastic/bgp https://docs.tigera.io/v3.4/reference/resources/packetcapture https://docs.tigera.io/v3.13/multicluster/federation/overview @@ -1412,7 +1412,7 @@ https://docs.tigera.io/v3.11/security/ https://docs.tigera.io/v3.13/getting-started/cnx/authentication-quickstart https://docs.tigera.io/v2.7/security/logs/elastic/dns https://docs.tigera.io/v3.12/networking/mtu -https://docs.tigera.io/v3.11/maintenance/monitor/prometheus/prometheus +https://docs.tigera.io/v3.11/maintenance/monitor/pickle/pickle https://docs.tigera.io/v3.12/security/simple-policy-cnx https://docs.tigera.io/v3.6/reference/host-endpoints/summary https://docs.tigera.io/v3.11/about/about-calico-enterprise @@ -1433,7 +1433,7 @@ https://docs.tigera.io/v3.2/getting-started/private-registry/private-registry-re https://docs.tigera.io/v3.13/security/training/about-kubernetes-services https://docs.tigera.io/v3.13/reference/resources/deeppacketinspection https://docs.tigera.io/v3.9/security/training/about-network-policy -https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/ +https://docs.tigera.io/v3.13/maintenance/monitor/pickle/ https://docs.tigera.io/v3.4/reference/public-cloud/gce https://docs.tigera.io/v3.9/threat/honeypod/ https://docs.tigera.io/v3.11/reference/host-endpoints/failsafe @@ -1586,7 +1586,7 @@ https://docs.tigera.io/v3.9/security/beginners https://docs.tigera.io/v3.13/reference/host-endpoints/pre-dnat https://docs.tigera.io/v3.9/security/ https://docs.tigera.io/v3.12/reference/resources/overview -https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/ +https://docs.tigera.io/v3.12/maintenance/monitor/pickle/ https://docs.tigera.io/v3.11/security/aws-integration/get-started https://docs.tigera.io/v3.11/reference/calicoctl/captured-packets https://docs.tigera.io/v3.12/security/comms/crypto-auth @@ -1618,7 +1618,7 @@ https://docs.tigera.io/v3.12/networking/bgp https://docs.tigera.io/v3.5/security/kubernetes-nodes https://docs.tigera.io/v3.13/reference/calicoctl/ipam/configure https://docs.tigera.io/v3.5/visibility/elastic/flow/datatypes -https://docs.tigera.io/v3.4/reference/felix/prometheus +https://docs.tigera.io/v3.4/reference/felix/pickle https://docs.tigera.io/v3.12/multicluster/federation/aws https://docs.tigera.io/v3.5/maintenance/upgrading-calico-to-calico-enterprise https://docs.tigera.io/v3.9/reference/calicoctl/version @@ -1695,7 +1695,7 @@ https://docs.tigera.io/v3.13/networking/bgp https://docs.tigera.io/v3.13/getting-started/windows-calico/kubernetes/standard https://docs.tigera.io/v3.9/reference/resources/profile https://docs.tigera.io/v3.13/threat/ -https://docs.tigera.io/v3.11/maintenance/monitor/prometheus/ +https://docs.tigera.io/v3.11/maintenance/monitor/pickle/ https://docs.tigera.io/v3.11/multicluster/mcm/fine-tune-deployment https://docs.tigera.io/v3.9/multicluster/mcm/configure https://docs.tigera.io/v3.3/reference/resources/kubecontrollersconfig @@ -1704,13 +1704,13 @@ https://docs.tigera.io/v3.11/networking/ipv6 https://docs.tigera.io/v3.13/threat/suspicious-ips https://docs.tigera.io/v3.9/security/fortinet-integration/firewall-integration https://docs.tigera.io/v3.12/reference/calicoctl/node/diags -https://docs.tigera.io/v3.6/reference/felix/prometheus +https://docs.tigera.io/v3.6/reference/felix/pickle https://docs.tigera.io/v3.11/threat/anomaly-detection/monitoring https://docs.tigera.io/v3.6/reference/host-endpoints/overview https://docs.tigera.io/v2.7/reference/cni-plugin/configuration https://docs.tigera.io/v3.4/security/aws-integration/metadata-access https://docs.tigera.io/v3.2/reference/host-endpoints/objects -https://docs.tigera.io/v3.12/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.12/reference/kube-controllers/pickle https://docs.tigera.io/v3.12/threat/ https://docs.tigera.io/v3.13/maintenance/clis/calicoq/configure/overview https://docs.tigera.io/v2.7/reference/calicoq/version @@ -1757,7 +1757,7 @@ https://docs.tigera.io/v3.13/getting-started/windows-calico/kubernetes/requireme https://docs.tigera.io/v3.13/reference/calicoq/selectors https://docs.tigera.io/v3.11/visibility/elastic/rbac-elasticsearch https://docs.tigera.io/v3.9/getting-started/windows-calico/demo -https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/byo-prometheus +https://docs.tigera.io/v3.13/maintenance/monitor/pickle/byo-pickle https://docs.tigera.io/v3.4/security/aws-integration/tiers-and-policy https://docs.tigera.io/v3.1/reference/architecture/overview https://docs.tigera.io/v3.11/visibility/iptables @@ -1799,7 +1799,7 @@ https://docs.tigera.io/v3.11/visibility/elastic/dns/filtering-dns https://docs.tigera.io/v3.6/visibility/elastic/filtering-dns https://docs.tigera.io/v3.13/visibility/elastic/flow/hep https://docs.tigera.io/v3.11/maintenance/kubernetes-upgrade-tsee/operator -https://docs.tigera.io/v3.6/maintenance/monitor/prometheus +https://docs.tigera.io/v3.6/maintenance/monitor/pickle https://docs.tigera.io/v3.6/reference/calicoctl/datastore/migrate/unlock https://docs.tigera.io/v3.12/visibility/elastic/bgp https://docs.tigera.io/v3.3/getting-started/openshift/requirements @@ -1843,7 +1843,7 @@ https://docs.tigera.io/v3.6/security/aws-integration/aws-security-group-integrat https://docs.tigera.io/v3.4/security/fortinet-integration/fortimgr-integration https://docs.tigera.io/v3.11/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.13/visibility/elastic/audit-overview -https://docs.tigera.io/v3.2/maintenance/monitor/prometheus +https://docs.tigera.io/v3.2/maintenance/monitor/pickle https://docs.tigera.io/v3.3/reference/resources/overview https://docs.tigera.io/v3.9/reference/resources/packetcapture https://docs.tigera.io/v3.9/reference/calicoctl/delete @@ -1873,7 +1873,7 @@ https://docs.tigera.io/v3.4/reference/resources/kubecontrollersconfig https://docs.tigera.io/v3.3/security/logs/elastic/view https://docs.tigera.io/v3.12/reference/calicoctl/version https://docs.tigera.io/v3.9/networking/bgp -https://docs.tigera.io/v3.9/maintenance/monitor/prometheus/ +https://docs.tigera.io/v3.9/maintenance/monitor/pickle/ https://docs.tigera.io/v3.9/networking/mtu https://docs.tigera.io/v3.9/reference/calicoctl/node/run https://docs.tigera.io/v3.5/visibility/elastic/filtering-dns @@ -1883,7 +1883,7 @@ https://docs.tigera.io/v2.7/getting-started/bare-metal/installation/container https://docs.tigera.io/v3.13/reference/faq https://docs.tigera.io/v3.12/compliance/ https://docs.tigera.io/v3.5/reference/calicoctl/node/diags -https://docs.tigera.io/v3.12/reference/felix/prometheus +https://docs.tigera.io/v3.12/reference/felix/pickle https://docs.tigera.io/v3.9/networking/training/about-kubernetes-networking https://docs.tigera.io/v3.13/getting-started/private-registry/private-registry-regular https://docs.tigera.io/v3.13/getting-started/kubernetes/rancher @@ -1941,7 +1941,7 @@ https://docs.tigera.io/v2.7/getting-started/kubernetes/requirements https://docs.tigera.io/v3.4/getting-started/kubernetes/aks https://docs.tigera.io/v3.9/security/comms/secure-bgp https://docs.tigera.io/v3.6/maintenance/troubleshoot/component-logs -https://docs.tigera.io/v3.9/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.9/reference/kube-controllers/pickle https://docs.tigera.io/v3.9/reference/ https://docs.tigera.io/v3.11/visibility/elastic/retention https://docs.tigera.io/v3.13/reference/host-endpoints/summary @@ -2045,7 +2045,7 @@ https://docs.tigera.io/v3.5/getting-started/openshift/ https://docs.tigera.io/v3.3/maintenance/clis/calicoctl/install https://docs.tigera.io/v3.11/maintenance/decommissioning-a-node https://docs.tigera.io/v3.5/getting-started/private-registry/private-registry-regular -https://docs.tigera.io/v3.11/reference/felix/prometheus +https://docs.tigera.io/v3.11/reference/felix/pickle https://docs.tigera.io/v3.9/multicluster/federation/services-controller https://docs.tigera.io/v3.11/reference/public-cloud/ https://docs.tigera.io/v3.13/maintenance/ebpf/ @@ -2192,7 +2192,7 @@ https://docs.tigera.io/v3.11/reference/calicoctl/node/overview https://docs.tigera.io/v3.13/reference/felix/ https://docs.tigera.io/v3.4/getting-started/openshift/ https://docs.tigera.io/v3.9/reference/component-resources/ -https://docs.tigera.io/v3.11/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.11/reference/kube-controllers/pickle https://docs.tigera.io/v3.13/security/tutorials/kubernetes-policy-advanced https://docs.tigera.io/v3.2/security/aws-integration/metadata-access https://docs.tigera.io/v3.12/security/fortinet-integration/fortimgr-integration @@ -2235,12 +2235,12 @@ https://docs.tigera.io/v3.11/reference/faq https://docs.tigera.io/v3.5/visibility/elastic/l7/datatypes https://docs.tigera.io/v3.13/getting-started/ https://docs.tigera.io/v3.12/visibility/elastic/flow/ -https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/prometheus +https://docs.tigera.io/v3.12/maintenance/monitor/pickle/pickle https://docs.tigera.io/v3.12/reference/public-cloud/gce -https://docs.tigera.io/v3.1/reference/felix/prometheus +https://docs.tigera.io/v3.1/reference/felix/pickle https://docs.tigera.io/v3.1/security/ingress https://docs.tigera.io/v3.9/reference/calicoctl/datastore/overview -https://docs.tigera.io/v3.13/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.13/reference/kube-controllers/pickle https://docs.tigera.io/v3.11/maintenance/clis/calicoctl/configure/ https://docs.tigera.io/v3.9/maintenance/clis/calicoctl/configure/ https://docs.tigera.io/v3.3/reference/calicoctl/node/status @@ -2352,7 +2352,7 @@ https://docs.tigera.io/v2.8/networking/custom-bgp-config https://docs.tigera.io/v3.5/maintenance/logstorage/log-storage-requirements https://docs.tigera.io/v3.13/maintenance/decommissioning-a-node https://docs.tigera.io/v3.6/maintenance/troubleshoot/troubleshoot-ebpf -https://docs.tigera.io/v3.9/maintenance/monitor/prometheus/alertmanager +https://docs.tigera.io/v3.9/maintenance/monitor/pickle/alertmanager https://docs.tigera.io/v3.6/getting-started/bare-metal/installation/container https://docs.tigera.io/v3.6/getting-started/kubernetes/gke https://docs.tigera.io/v3.12/multicluster/mcm/fine-tune-deployment @@ -2493,7 +2493,7 @@ https://docs.tigera.io/v3.8/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/v3.10/maintenance/monitor/metrics/license-agent https://docs.tigera.io/v3.8/reference/resources/globalnetworkpolicy https://docs.tigera.io/v3.8/reference/calicoctl/replace -https://docs.tigera.io/v3.8/maintenance/monitor/prometheus/prometheus +https://docs.tigera.io/v3.8/maintenance/monitor/pickle/pickle https://docs.tigera.io/v3.8/visibility/elastic/archive-storage https://docs.tigera.io/v3.8/getting-started/bare-metal/ https://docs.tigera.io/v3.10/maintenance/logstorage/ @@ -2582,7 +2582,7 @@ https://docs.tigera.io/v3.10/security/aws-integration/get-started https://docs.tigera.io/v3.10/reference/calicoctl/ipam/check https://docs.tigera.io/v3.8/getting-started/kubernetes/quickstart https://docs.tigera.io/v3.10/reference/dikastes/configuration -https://docs.tigera.io/v3.10/reference/kube-controllers/prometheus +https://docs.tigera.io/v3.10/reference/kube-controllers/pickle https://docs.tigera.io/v3.8/security/tutorials/kubernetes-policy-advanced https://docs.tigera.io/v3.10/reference/resources/workloadendpoint https://docs.tigera.io/v3.8/security/ @@ -2623,7 +2623,7 @@ https://docs.tigera.io/v3.10/getting-started/install-on-clusters/ https://docs.tigera.io/v3.8/reference/felix/ https://docs.tigera.io/v3.8/reference/resources/workloadendpoint https://docs.tigera.io/v3.10/threat/ -https://docs.tigera.io/v3.10/reference/felix/prometheus +https://docs.tigera.io/v3.10/reference/felix/pickle https://docs.tigera.io/v3.8/reference/calicoq/policy https://docs.tigera.io/v3.8/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.10/reference/calicoctl/ipam/release @@ -2664,7 +2664,7 @@ https://docs.tigera.io/v3.8/maintenance/troubleshoot/ https://docs.tigera.io/v3.10/security/comms/certificate-management https://docs.tigera.io/v3.8/security/tiered-policy https://docs.tigera.io/v3.10/reference/host-endpoints/objects -https://docs.tigera.io/v3.8/reference/felix/prometheus +https://docs.tigera.io/v3.8/reference/felix/pickle https://docs.tigera.io/v3.10/reference/public-cloud/azure https://docs.tigera.io/v3.10/visibility/elastic/kube-audit https://docs.tigera.io/v3.10/policy/ @@ -2704,11 +2704,11 @@ https://docs.tigera.io/v3.10/maintenance/clis/calicoctl/ https://docs.tigera.io/v3.8/threat/suspicious-ips https://docs.tigera.io/v3.8/security/comms/crypto-auth https://docs.tigera.io/v3.10/maintenance/monitor/metrics/bgp-metrics -https://docs.tigera.io/v3.8/maintenance/monitor/prometheus/ +https://docs.tigera.io/v3.8/maintenance/monitor/pickle/ https://docs.tigera.io/v3.8/maintenance/ebpf/ https://docs.tigera.io/v3.8/security/tutorials/kubernetes-policy-basic https://docs.tigera.io/v3.10/reference/resources/globalnetworkpolicy -https://docs.tigera.io/v3.8/maintenance/monitor/prometheus/alertmanager +https://docs.tigera.io/v3.8/maintenance/monitor/pickle/alertmanager https://docs.tigera.io/v3.10/about/about-calico-enterprise https://docs.tigera.io/v3.8/security/tutorials/app-layer-policy/enforce-policy-istio https://docs.tigera.io/v3.8/getting-started/private-registry/private-registry-image-path @@ -3013,7 +3013,7 @@ https://docs.tigera.io/archive/v3.18/reference/etcd-rbac/calico-etcdv3-paths https://docs.tigera.io/archive/v3.22/getting-started/windows-calico/demo https://docs.tigera.io/archive/v3.19/security/tutorials/kubernetes-policy-advanced https://docs.tigera.io/archive/v3.17/reference/calicoctl/node/status -https://docs.tigera.io/archive/v3.13/reference/felix/prometheus +https://docs.tigera.io/archive/v3.13/reference/felix/pickle https://docs.tigera.io/archive/v3.22/maintenance/install-apiserver https://docs.tigera.io/archive/v3.19/reference/calicoctl/patch https://docs.tigera.io/archive/v3.19/getting-started/bare-metal/installation/binary @@ -3242,7 +3242,7 @@ https://docs.tigera.io/archive/v3.14/getting-started/kubernetes/installation/con https://docs.tigera.io/archive/v3.19/getting-started/kubernetes/hardway/configure-bgp-peering https://docs.tigera.io/archive/v3.20/reference/calicoctl/node/overview https://docs.tigera.io/archive/v3.17/reference/architecture/overview -https://docs.tigera.io/v3.12/maintenance/monitor/prometheus +https://docs.tigera.io/v3.12/maintenance/monitor/pickle https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/hardway/the-calico-datastore https://docs.tigera.io/archive/v3.12/reference/typha/configuration https://docs.tigera.io/archive/v3.19/reference/calicoctl/replace @@ -3273,7 +3273,7 @@ https://docs.tigera.io/archive/v3.23/reference/resources/node https://docs.tigera.io/archive/v3.15/getting-started/openshift/installation https://docs.tigera.io/archive/v3.22/reference/calicoctl/get https://docs.tigera.io/archive/v3.23/reference/public-cloud/ -https://docs.tigera.io/archive/v3.22/reference/kube-controllers/prometheus +https://docs.tigera.io/archive/v3.22/reference/kube-controllers/pickle https://docs.tigera.io/archive/v3.19/reference/host-endpoints/connectivity https://docs.tigera.io/archive/v3.20/security/kubernetes-default-deny https://docs.tigera.io/archive/v3.22/maintenance/troubleshoot/troubleshooting @@ -3288,7 +3288,7 @@ https://docs.tigera.io/archive/v3.21/reference/legal/node https://docs.tigera.io/archive/v3.22/reference/host-endpoints/summary https://docs.tigera.io/archive/v3.12/networking/ https://docs.tigera.io/archive/v3.13/reference/architecture/overview -https://docs.tigera.io/archive/v3.20/reference/felix/prometheus +https://docs.tigera.io/archive/v3.20/reference/felix/pickle https://docs.tigera.io/archive/v3.20/security/tutorials/protect-hosts https://docs.tigera.io/archive/v3.14/networking/openstack/configuration https://docs.tigera.io/archive/v3.12/security/comms/reduce-nodes @@ -3427,7 +3427,7 @@ https://docs.tigera.io/archive/v3.13/reference/host-endpoints/pre-dnat https://docs.tigera.io/archive/v3.15/reference/calicoctl/node/diags https://docs.tigera.io/archive/v3.22/reference/calicoctl/delete https://docs.tigera.io/archive/v3.19/getting-started/windows-calico/openshift/ -https://docs.tigera.io/archive/v3.14/reference/felix/prometheus +https://docs.tigera.io/archive/v3.14/reference/felix/pickle https://docs.tigera.io/archive/v3.22/reference/faq https://docs.tigera.io/archive/v3.18/getting-started/kubernetes/hardway/configure-ip-pools https://docs.tigera.io/archive/v3.22/reference/resources/networkpolicy @@ -3483,7 +3483,7 @@ https://docs.tigera.io/archive/v3.15/getting-started/openstack/requirements https://docs.tigera.io/archive/v3.22/getting-started/windows-calico/limitations https://docs.tigera.io/archive/v3.16/reference/etcd-rbac/kubernetes-advanced https://docs.tigera.io/archive/v3.13/reference/calicoctl/apply -https://docs.tigera.io/archive/v3.15/reference/felix/prometheus +https://docs.tigera.io/archive/v3.15/reference/felix/pickle https://docs.tigera.io/archive/v3.16/getting-started/clis/calicoctl/ https://docs.tigera.io/archive/v3.14/networking/bgp https://docs.tigera.io/archive/v3.16/reference/host-endpoints/failsafe @@ -3573,7 +3573,7 @@ https://docs.tigera.io/archive/v3.22/getting-started/kubernetes/hardway/install- https://docs.tigera.io/archive/v3.22/maintenance/troubleshoot/commands https://docs.tigera.io/archive/v3.20/getting-started/kubernetes/k3s/multi-node-install https://docs.tigera.io/archive/v3.22/security/comms/ -https://docs.tigera.io/archive/v3.22/reference/felix/prometheus +https://docs.tigera.io/archive/v3.22/reference/felix/pickle https://docs.tigera.io/archive/v3.21/getting-started/openstack/installation/ubuntu https://docs.tigera.io/archive/v3.13/reference/faq https://docs.tigera.io/archive/v3.13/maintenance/kubernetes-upgrade @@ -3987,15 +3987,15 @@ https://docs.tigera.io/archive/v3.20/getting-started/windows-calico/openshift/in https://docs.tigera.io/archive/v3.16/reference/public-cloud/azure https://docs.tigera.io/archive/v3.18/networking/openstack/dev-machine-setup https://docs.tigera.io/archive/v3.18/networking/ipv6 -https://docs.tigera.io/archive/v3.23/reference/felix/prometheus +https://docs.tigera.io/archive/v3.23/reference/felix/pickle https://docs.tigera.io/archive/v3.22/release-notes/ https://docs.tigera.io/archive/v3.23/reference/host-endpoints/forwarded -https://docs.tigera.io/archive/v3.18/reference/kube-controllers/prometheus +https://docs.tigera.io/archive/v3.18/reference/kube-controllers/pickle https://docs.tigera.io/v3.12/getting-started/openshift/installation/index https://docs.tigera.io/archive/v3.20/getting-started/kubernetes/installation/config-options https://docs.tigera.io/archive/v3.12/reference/dikastes/configuration https://docs.tigera.io/archive/v3.20/reference/etcd-rbac/calico-etcdv3-paths -https://docs.tigera.io/archive/v3.20/reference/kube-controllers/prometheus +https://docs.tigera.io/archive/v3.20/reference/kube-controllers/pickle https://docs.tigera.io/archive/v3.22/getting-started/openstack/installation/overview https://docs.tigera.io/archive/v3.12/reference/involved https://docs.tigera.io/archive/v3.13/networking/use-ipvs @@ -4015,7 +4015,7 @@ https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/installation/con https://docs.tigera.io/archive/v3.20/reference/legal/node https://docs.tigera.io/v3.12/maintenance/monitor/metrics https://docs.tigera.io/archive/v3.21/getting-started/kubernetes/hardway/configure-bgp-peering -https://docs.tigera.io/archive/v3.23/reference/kube-controllers/prometheus +https://docs.tigera.io/archive/v3.23/reference/kube-controllers/pickle https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/hardway/configure-ip-pools https://docs.tigera.io/archive/v3.18/getting-started/kubernetes/hardway/install-node https://docs.tigera.io/v3.9/reference @@ -4054,7 +4054,7 @@ https://docs.tigera.io/archive/v3.19/networking/workloads-outside-cluster https://docs.tigera.io/v3.7/getting-started/cnx//access-the-manager https://docs.tigera.io/archive/v3.20/reference/calicoctl/create https://docs.tigera.io/archive/v3.21/networking/openstack/ -https://docs.tigera.io/v3.13/maintenance/monitor/prometheus +https://docs.tigera.io/v3.13/maintenance/monitor/pickle https://docs.tigera.io/archive/v3.12/getting-started/openshift/ https://docs.tigera.io/archive/v3.12/getting-started/bare-metal/installation/binary https://docs.tigera.io/archive/v3.17/reference/resources/globalnetworkset @@ -4075,7 +4075,7 @@ https://docs.tigera.io/archive/v3.17/getting-started/windows-calico/kubernetes/r https://docs.tigera.io/archive/v3.21/reference/etcd-rbac/overview https://docs.tigera.io/archive/v3.14/reference/host-endpoints/pre-dnat https://docs.tigera.io/archive/v3.22/getting-started/kubernetes/k3s/multi-node-install -https://docs.tigera.io/archive/v3.21/reference/kube-controllers/prometheus +https://docs.tigera.io/archive/v3.21/reference/kube-controllers/pickle https://docs.tigera.io/archive/v3.14/reference/calicoctl/ipam/configure https://docs.tigera.io/archive/v3.12/reference/resources/felixconfig https://docs.tigera.io/archive/v3.14/reference/calicoctl/ipam/overview @@ -4148,7 +4148,7 @@ https://docs.tigera.io/archive/v3.23/getting-started/kubernetes/minikube https://docs.tigera.io/archive/v3.13/reference/host-endpoints/selector https://docs.tigera.io/archive/v3.23/reference/legal/node https://docs.tigera.io/archive/v3.12/getting-started/openstack/requirements -https://docs.tigera.io/archive/v3.12/reference/felix/prometheus +https://docs.tigera.io/archive/v3.12/reference/felix/pickle https://docs.tigera.io/archive/v3.17/getting-started/kubernetes/hardway/install-node https://docs.tigera.io/archive/v3.14/reference/calicoctl/ipam/release https://docs.tigera.io/archive/v3.23/maintenance/clis/calicoctl @@ -4246,7 +4246,7 @@ https://docs.tigera.io/archive/v3.15/reference/calicoctl/ipam/release https://docs.tigera.io/archive/v3.22/networking/openstack/semantics https://docs.tigera.io/archive/v3.21/networking/openstack/configuration https://docs.tigera.io/archive/v3.20/security/ -https://docs.tigera.io/archive/v3.18/reference/felix/prometheus +https://docs.tigera.io/archive/v3.18/reference/felix/pickle https://docs.tigera.io/archive/v3.22/getting-started/openshift/requirements https://docs.tigera.io/archive/v3.23/reference/ https://docs.tigera.io/archive/v3.23/getting-started/windows-calico/kubernetes/requirements @@ -4348,7 +4348,7 @@ https://docs.tigera.io/archive/v3.19/maintenance/openstack-upgrade https://docs.tigera.io/archive/v3.22/reference/resources/networkset https://docs.tigera.io/archive/v3.12/reference/calicoctl/overview https://docs.tigera.io/archive/v3.23/security/tutorials/kubernetes-policy-advanced -https://docs.tigera.io/archive/v3.19/reference/felix/prometheus +https://docs.tigera.io/archive/v3.19/reference/felix/pickle https://docs.tigera.io/archive/v3.20/networking https://docs.tigera.io/archive/v3.15/getting-started/kubernetes/hardway/the-calico-datastore https://docs.tigera.io/archive/v3.23/getting-started/openstack/verification @@ -4391,7 +4391,7 @@ https://docs.tigera.io/archive/v3.14/security/tutorials/app-layer-policy/enforce https://docs.tigera.io/archive/v3.21/getting-started/kubernetes/helm https://docs.tigera.io/archive/v3.16/getting-started/kubernetes/hardway/install-typha https://docs.tigera.io/archive/v3.23/getting-started/kubernetes/hardway/istio-integration -https://docs.tigera.io/v3.11/maintenance/monitor/prometheus +https://docs.tigera.io/v3.11/maintenance/monitor/pickle https://docs.tigera.io/archive/v3.15/reference/resources/networkpolicy https://docs.tigera.io/archive/v3.22/networking/openstack/floating-ips https://docs.tigera.io/archive/v3.22/getting-started/ @@ -4412,7 +4412,7 @@ https://docs.tigera.io/archive/v3.19/reference/node/configuration https://docs.tigera.io/archive/v3.23/about/ https://docs.tigera.io/archive/v3.21/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/archive/v3.17/networking/openstack/configuration -https://docs.tigera.io/archive/v3.17/reference/felix/prometheus +https://docs.tigera.io/archive/v3.17/reference/felix/pickle https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/hardway/install-node https://docs.tigera.io/archive/v3.20/networking/openstack/configuration https://docs.tigera.io/archive/v3.19/reference/calicoctl/label @@ -4445,7 +4445,7 @@ https://docs.tigera.io/archive/v3.23/getting-started/kubernetes/k3s/multi-node-i https://docs.tigera.io/archive/v3.15/networking/workloads-outside-cluster https://docs.tigera.io/archive/v3.17/maintenance/troubleshoot/troubleshoot-ebpf https://docs.tigera.io/archive/v3.18/reference/host-endpoints/forwarded -https://docs.tigera.io/v3.9/maintenance/monitor/prometheus +https://docs.tigera.io/v3.9/maintenance/monitor/pickle https://docs.tigera.io/archive/v3.16/getting-started/clis/calicoctl/configure/overview https://docs.tigera.io/archive/v3.22/security/comms/crypto-auth https://docs.tigera.io/archive/v3.18/maintenance/ diff --git a/calico-cloud/_includes/components/FelixConfig/config-params.json b/calico-cloud/_includes/components/FelixConfig/config-params.json index 8f6cd44252..02ae543838 100644 --- a/calico-cloud/_includes/components/FelixConfig/config-params.json +++ b/calico-cloud/_includes/components/FelixConfig/config-params.json @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1216,7 +1216,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1243,7 +1243,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1270,7 +1270,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6036,7 +6036,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6063,7 +6063,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6090,7 +6090,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6117,7 +6117,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6144,7 +6144,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-cloud/get-started/operator-checklist.mdx b/calico-cloud/get-started/operator-checklist.mdx index 4eab76a9c0..c1c1967aee 100644 --- a/calico-cloud/get-started/operator-checklist.mdx +++ b/calico-cloud/get-started/operator-checklist.mdx @@ -534,10 +534,10 @@ cmEtdm9sdHJvbjAeFw0yMDEyMjExOTA1MzhaFw0yNTEyMjAxOTA1MzhaMBkxFzAV **8 - monitor** -`monitor` is responsible for configuring prometheus and associated custom resources. Check the pods and logs in the `tigera-prometheus` namespace. +`monitor` is responsible for configuring pickle and associated custom resources. Check the pods and logs in the `tigera-pickle` namespace. ```bash -$ kubectl get pods -n tigera-prometheus +$ kubectl get pods -n tigera-pickle ``` ``` @@ -545,8 +545,8 @@ NAME READY STATUS RESTARTS AGE alertmanager-calico-node-alertmanager-0 2/2 Running 0 125m alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ### Check additional custom resources @@ -589,7 +589,7 @@ default 120m The installation script deploys a Prometheus operator and associated custom resources. If you already have a Prometheus operator running in your cluster, contact Tigera support. ```bash -kubectl get pods -n tigera-prometheus +kubectl get pods -n tigera-pickle ``` ``` @@ -597,8 +597,8 @@ NAME READY STATUS RESTARTS AGE alertmanager-calico-node-alertmanager-0 2/2 Running 0 125m alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ## Check pod capacity @@ -608,7 +608,7 @@ If cluster does not have enough capacity, it will not be able to deploy pods. Th The high-level components $[prodname] needs to run are: - Per node: 1 fluentd, 1 compliance benchmarker -- On top of per node: 3 alertmanager (from statefulset), 1 prometheus, 1 prometheus operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver +- On top of per node: 3 alertmanager (from statefulset), 1 pickle, 1 pickle operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver Some clusters have limited pod-networked pod capacity. diff --git a/calico-cloud/network-policy/beginners/simple-policy-cnx.mdx b/calico-cloud/network-policy/beginners/simple-policy-cnx.mdx index fdb7654ba2..b2b567b9e6 100644 --- a/calico-cloud/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-cloud/network-policy/beginners/simple-policy-cnx.mdx @@ -94,15 +94,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -120,7 +120,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx b/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx index 01cd6ccaf3..3a3a3e6b50 100644 --- a/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx index f8a2256055..1ec06b87d2 100644 --- a/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) diff --git a/calico-cloud/operations/comms/index.mdx b/calico-cloud/operations/comms/index.mdx index 5c0aeee98e..c4779edcc6 100644 --- a/calico-cloud/operations/comms/index.mdx +++ b/calico-cloud/operations/comms/index.mdx @@ -49,14 +49,14 @@ The **Deployed to** column shows the namespace where the operator places the sec |---|---|---|---| | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `node-certs` | `typha-client` | `calico-system` | Installation/default | | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | | `typha-certs` | `typha-server` | `calico-system` | Installation/default | | `typha-certs-noncluster-host` | `typha-server-noncluster-host` | `calico-system` | Installation/default | diff --git a/calico-cloud/operations/disconnect.mdx b/calico-cloud/operations/disconnect.mdx index c63f8cdc8c..4b14e1a726 100644 --- a/calico-cloud/operations/disconnect.mdx +++ b/calico-cloud/operations/disconnect.mdx @@ -48,7 +48,7 @@ not be successful. You will need to reach out to your support contact to create 1. Run the script and read the help to determine if you need to specify any flags `./downgrade.sh --help`. -1. Run the script with any needed flags, for example: `./downgrade.sh --remove-prometheus`. +1. Run the script with any needed flags, for example: `./downgrade.sh --remove-pickle`. ## Next steps diff --git a/calico-cloud/operations/index.mdx b/calico-cloud/operations/index.mdx index f8da8da396..3e97c60090 100644 --- a/calico-cloud/operations/index.mdx +++ b/calico-cloud/operations/index.mdx @@ -18,11 +18,11 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring - + - - - + + + diff --git a/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx b/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx index 74def9953e..0905c7faec 100644 --- a/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -154,4 +154,4 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-cloud/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-cloud/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 842f83e06b..b5606f75db 100644 --- a/calico-cloud/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -29,11 +29,11 @@ The following example creates a Prometheus rule to monitor some important Fluent apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-cloud/operations/monitor/metrics/policy-metrics.mdx b/calico-cloud/operations/monitor/metrics/policy-metrics.mdx index fc49d366a1..3e094a2aad 100644 --- a/calico-cloud/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-cloud/operations/monitor/prometheus/alertmanager.mdx b/calico-cloud/operations/monitor/prometheus/alertmanager.mdx index 49b5fb329c..e94fa0f143 100644 --- a/calico-cloud/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-cloud/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Cloud connected cluster to route Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx index bfcc5039f5..09329ac659 100644 --- a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -306,11 +306,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -341,11 +341,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -358,7 +358,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -375,9 +375,9 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Port-forward the Prometheus pods and run this command with the forwarded port. diff --git a/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx index b9b3579431..a91ef9ac47 100644 --- a/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -32,10 +32,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -57,10 +57,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: tigera-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: tigera-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-cloud/operations/monitor/prometheus/support.mdx b/calico-cloud/operations/monitor/prometheus/support.mdx index cde1d72c4e..e3dc07855d 100644 --- a/calico-cloud/operations/monitor/prometheus/support.mdx +++ b/calico-cloud/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Cloud connected clusters ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,6 +14,6 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. - If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. + If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](byo-prometheus.mdx) +- [Bring your own Prometheus](byo-pickle.mdx) diff --git a/calico-cloud/reference/attribution.mdx b/calico-cloud/reference/attribution.mdx index c66b171c27..511c58de91 100644 --- a/calico-cloud/reference/attribution.mdx +++ b/calico-cloud/reference/attribution.mdx @@ -1426,8 +1426,8 @@ In the table below, you can look at the details of each project and license asso Tigera Proprietary - github.com/prometheus/client_golang/ - github.com/prometheus/client_golang/prometheus-v1.7.1 + github.com/pickle/client_golang/ + github.com/pickle/client_golang/pickle-v1.7.1 Apache 2.0 diff --git a/calico-cloud/reference/component-resources/kube-controllers/index.mdx b/calico-cloud/reference/component-resources/kube-controllers/index.mdx index c42646d765..bca2123a45 100644 --- a/calico-cloud/reference/component-resources/kube-controllers/index.mdx +++ b/calico-cloud/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). diff --git a/calico-cloud/reference/index.mdx b/calico-cloud/reference/index.mdx index 96baeba785..5f6d4e9f72 100644 --- a/calico-cloud/reference/index.mdx +++ b/calico-cloud/reference/index.mdx @@ -65,10 +65,10 @@ APIs, CLI, architecture and design, and FAQ. - + - + ## Configuration on public clouds diff --git a/calico-cloud/reference/installation/_api.mdx b/calico-cloud/reference/installation/_api.mdx index 12b94aa5c6..03f65ba63e 100644 --- a/calico-cloud/reference/installation/_api.mdx +++ b/calico-cloud/reference/installation/_api.mdx @@ -854,7 +854,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -949,7 +949,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1120,11 +1120,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2541,7 +2541,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2600,7 +2600,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3592,8 +3592,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4635,8 +4635,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5207,7 +5207,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5217,7 +5217,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5232,11 +5232,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5361,12 +5361,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-cloud/reference/resources/kubecontrollersconfig.mdx b/calico-cloud/reference/resources/kubecontrollersconfig.mdx index 4c9b4aac13..b0b21a21fa 100644 --- a/calico-cloud/reference/resources/kubecontrollersconfig.mdx +++ b/calico-cloud/reference/resources/kubecontrollersconfig.mdx @@ -24,7 +24,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -64,7 +64,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-cloud/releases.json b/calico-cloud/releases.json index ce9c8cbf30..e59c08419c 100644 --- a/calico-cloud/releases.json +++ b/calico-cloud/releases.json @@ -166,29 +166,29 @@ "image": "tigera/packetcapture", "version": "v3.21.0-1.0" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "v3.21.0-1.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.43.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.62.0" }, "coreos-config-reloader": { "version": "v0.62.0" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "v3.21.0-1.0" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "v3.21.0-1.0" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "v3.21.0-1.0" }, "es-gateway": { diff --git a/calico-cloud/threat/configuring-webhooks.mdx b/calico-cloud/threat/configuring-webhooks.mdx index 3f0cf16d61..4a55693b8a 100644 --- a/calico-cloud/threat/configuring-webhooks.mdx +++ b/calico-cloud/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-cloud_versioned_docs/version-22-2/_includes/components/FelixConfig/config-params.json b/calico-cloud_versioned_docs/version-22-2/_includes/components/FelixConfig/config-params.json index 3c28de306c..e8141cf717 100644 --- a/calico-cloud_versioned_docs/version-22-2/_includes/components/FelixConfig/config-params.json +++ b/calico-cloud_versioned_docs/version-22-2/_includes/components/FelixConfig/config-params.json @@ -973,7 +973,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1000,7 +1000,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -5572,7 +5572,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5599,7 +5599,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5626,7 +5626,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -5653,7 +5653,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5680,7 +5680,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-cloud_versioned_docs/version-22-2/get-started/operator-checklist.mdx b/calico-cloud_versioned_docs/version-22-2/get-started/operator-checklist.mdx index 186d3dc847..a1dc34a7c6 100644 --- a/calico-cloud_versioned_docs/version-22-2/get-started/operator-checklist.mdx +++ b/calico-cloud_versioned_docs/version-22-2/get-started/operator-checklist.mdx @@ -557,10 +557,10 @@ cmEtdm9sdHJvbjAeFw0yMDEyMjExOTA1MzhaFw0yNTEyMjAxOTA1MzhaMBkxFzAV **8 - monitor** -`monitor` is responsible for configuring prometheus and associated custom resources. Check the pods and logs in the `tigera-prometheus` namespace. +`monitor` is responsible for configuring pickle and associated custom resources. Check the pods and logs in the `tigera-pickle` namespace. ```bash -$ kubectl get pods -n tigera-prometheus +$ kubectl get pods -n tigera-pickle ``` ``` @@ -568,8 +568,8 @@ NAME READY STATUS RESTARTS AGE alertmanager-calico-node-alertmanager-0 2/2 Running 0 125m alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` **9 - runtime-security** @@ -625,7 +625,7 @@ default 120m The installation script deploys a Prometheus operator and associated custom resources. If you already have a Prometheus operator running in your cluster, contact Tigera support. ```bash -kubectl get pods -n tigera-prometheus +kubectl get pods -n tigera-pickle ``` ``` @@ -633,8 +633,8 @@ NAME READY STATUS RESTARTS AGE alertmanager-calico-node-alertmanager-0 2/2 Running 0 125m alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ## Check pod capacity @@ -644,7 +644,7 @@ If cluster does not have enough capacity, it will not be able to deploy pods. Th The high-level components $[prodname] needs to run are: - Per node: 1 fluentd, 1 compliance benchmarker -- On top of per node: 3 alertmanager (from statefulset), 1 prometheus, 1 prometheus operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver +- On top of per node: 3 alertmanager (from statefulset), 1 pickle, 1 pickle operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver Some clusters have limited pod-networked pod capacity. diff --git a/calico-cloud_versioned_docs/version-22-2/network-policy/beginners/simple-policy-cnx.mdx b/calico-cloud_versioned_docs/version-22-2/network-policy/beginners/simple-policy-cnx.mdx index fdb7654ba2..b2b567b9e6 100644 --- a/calico-cloud_versioned_docs/version-22-2/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-cloud_versioned_docs/version-22-2/network-policy/beginners/simple-policy-cnx.mdx @@ -94,15 +94,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -120,7 +120,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-cloud_versioned_docs/version-22-2/operations/comms/secure-metrics.mdx b/calico-cloud_versioned_docs/version-22-2/operations/comms/secure-metrics.mdx index 9b1200b1f0..67d92f5185 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/comms/secure-metrics.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/comms/secure-metrics.mdx @@ -136,9 +136,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -146,7 +146,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -159,33 +159,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -197,9 +197,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -212,7 +212,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -220,7 +220,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -233,21 +233,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -255,13 +255,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -275,7 +275,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -291,7 +291,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -375,15 +375,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -395,32 +395,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -432,9 +432,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -446,13 +446,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -463,20 +463,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -484,13 +484,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -501,7 +501,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -510,5 +510,5 @@ spec: Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico-cloud_versioned_docs/version-22-2/operations/disconnect.mdx b/calico-cloud_versioned_docs/version-22-2/operations/disconnect.mdx index c63f8cdc8c..4b14e1a726 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/disconnect.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/disconnect.mdx @@ -48,7 +48,7 @@ not be successful. You will need to reach out to your support contact to create 1. Run the script and read the help to determine if you need to specify any flags `./downgrade.sh --help`. -1. Run the script with any needed flags, for example: `./downgrade.sh --remove-prometheus`. +1. Run the script with any needed flags, for example: `./downgrade.sh --remove-pickle`. ## Next steps diff --git a/calico-cloud_versioned_docs/version-22-2/operations/index.mdx b/calico-cloud_versioned_docs/version-22-2/operations/index.mdx index bd493f19ba..8afca631fe 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/index.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/index.mdx @@ -25,11 +25,11 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring - + - - - + + + diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx index 2fc0c6a6fa..ca5690981f 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -155,4 +155,4 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 842f83e06b..b5606f75db 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -29,11 +29,11 @@ The following example creates a Prometheus rule to monitor some important Fluent apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx index fc49d366a1..3e094a2aad 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx index 49b5fb329c..e94fa0f143 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Cloud connected cluster to route Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx index 2c674391c6..40bc9364d8 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -306,11 +306,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -341,11 +341,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -358,7 +358,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -375,8 +375,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx index 7d244318a9..8caca4c51c 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -31,11 +31,11 @@ As an example, the range query in this Manifest is 10 seconds. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -56,11 +56,11 @@ To update this alerting rule, to say, execute the query with a range of apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: tigera-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: tigera-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx index cde1d72c4e..e3dc07855d 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Cloud connected clusters ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,6 +14,6 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. - If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. + If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](byo-prometheus.mdx) +- [Bring your own Prometheus](byo-pickle.mdx) diff --git a/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx b/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx index c66b171c27..511c58de91 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx @@ -1426,8 +1426,8 @@ In the table below, you can look at the details of each project and license asso Tigera Proprietary - github.com/prometheus/client_golang/ - github.com/prometheus/client_golang/prometheus-v1.7.1 + github.com/pickle/client_golang/ + github.com/pickle/client_golang/pickle-v1.7.1 Apache 2.0 diff --git a/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx b/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx index c42646d765..bca2123a45 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). diff --git a/calico-cloud_versioned_docs/version-22-2/reference/index.mdx b/calico-cloud_versioned_docs/version-22-2/reference/index.mdx index 973c1bc0ce..466c054ca6 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/index.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/index.mdx @@ -68,10 +68,10 @@ APIs, CLI, architecture and design, and FAQ. - + - + ## Configuration on public clouds diff --git a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx index 221c4f4a5d..57f97bab95 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx @@ -854,7 +854,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -949,7 +949,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1120,11 +1120,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2541,7 +2541,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2600,7 +2600,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3592,8 +3592,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4635,8 +4635,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5207,7 +5207,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5217,7 +5217,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5232,11 +5232,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5361,12 +5361,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-cloud_versioned_docs/version-22-2/reference/resources/kubecontrollersconfig.mdx b/calico-cloud_versioned_docs/version-22-2/reference/resources/kubecontrollersconfig.mdx index 80f3885720..b376b3aaf5 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/resources/kubecontrollersconfig.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/resources/kubecontrollersconfig.mdx @@ -24,7 +24,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -62,7 +62,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-cloud_versioned_docs/version-22-2/releases.json b/calico-cloud_versioned_docs/version-22-2/releases.json index bf80670ee7..5aaf1c309d 100644 --- a/calico-cloud_versioned_docs/version-22-2/releases.json +++ b/calico-cloud_versioned_docs/version-22-2/releases.json @@ -79,10 +79,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -218,17 +218,17 @@ "version": "v3.22.1", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.1", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.1", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.1", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.1", @@ -238,9 +238,9 @@ "version": "v3.22.1", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.1", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.1", @@ -344,10 +344,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -483,17 +483,17 @@ "version": "v3.22-2.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22-2.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22-2.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22-2.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22-2.0", @@ -503,9 +503,9 @@ "version": "v3.22-2.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22-2.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22-2.0", diff --git a/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx b/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx index 3f0cf16d61..4a55693b8a 100644 --- a/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx +++ b/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-cloud_versioned_docs/version-23-2/_includes/components/FelixConfig/config-params.json b/calico-cloud_versioned_docs/version-23-2/_includes/components/FelixConfig/config-params.json index 8f6cd44252..02ae543838 100644 --- a/calico-cloud_versioned_docs/version-23-2/_includes/components/FelixConfig/config-params.json +++ b/calico-cloud_versioned_docs/version-23-2/_includes/components/FelixConfig/config-params.json @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1216,7 +1216,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1243,7 +1243,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1270,7 +1270,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6036,7 +6036,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6063,7 +6063,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6090,7 +6090,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6117,7 +6117,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6144,7 +6144,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-cloud_versioned_docs/version-23-2/get-started/operator-checklist.mdx b/calico-cloud_versioned_docs/version-23-2/get-started/operator-checklist.mdx index 4eab76a9c0..c1c1967aee 100644 --- a/calico-cloud_versioned_docs/version-23-2/get-started/operator-checklist.mdx +++ b/calico-cloud_versioned_docs/version-23-2/get-started/operator-checklist.mdx @@ -534,10 +534,10 @@ cmEtdm9sdHJvbjAeFw0yMDEyMjExOTA1MzhaFw0yNTEyMjAxOTA1MzhaMBkxFzAV **8 - monitor** -`monitor` is responsible for configuring prometheus and associated custom resources. Check the pods and logs in the `tigera-prometheus` namespace. +`monitor` is responsible for configuring pickle and associated custom resources. Check the pods and logs in the `tigera-pickle` namespace. ```bash -$ kubectl get pods -n tigera-prometheus +$ kubectl get pods -n tigera-pickle ``` ``` @@ -545,8 +545,8 @@ NAME READY STATUS RESTARTS AGE alertmanager-calico-node-alertmanager-0 2/2 Running 0 125m alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ### Check additional custom resources @@ -589,7 +589,7 @@ default 120m The installation script deploys a Prometheus operator and associated custom resources. If you already have a Prometheus operator running in your cluster, contact Tigera support. ```bash -kubectl get pods -n tigera-prometheus +kubectl get pods -n tigera-pickle ``` ``` @@ -597,8 +597,8 @@ NAME READY STATUS RESTARTS AGE alertmanager-calico-node-alertmanager-0 2/2 Running 0 125m alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ## Check pod capacity @@ -608,7 +608,7 @@ If cluster does not have enough capacity, it will not be able to deploy pods. Th The high-level components $[prodname] needs to run are: - Per node: 1 fluentd, 1 compliance benchmarker -- On top of per node: 3 alertmanager (from statefulset), 1 prometheus, 1 prometheus operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver +- On top of per node: 3 alertmanager (from statefulset), 1 pickle, 1 pickle operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver Some clusters have limited pod-networked pod capacity. diff --git a/calico-cloud_versioned_docs/version-23-2/network-policy/beginners/simple-policy-cnx.mdx b/calico-cloud_versioned_docs/version-23-2/network-policy/beginners/simple-policy-cnx.mdx index fdb7654ba2..b2b567b9e6 100644 --- a/calico-cloud_versioned_docs/version-23-2/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-cloud_versioned_docs/version-23-2/network-policy/beginners/simple-policy-cnx.mdx @@ -94,15 +94,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -120,7 +120,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx b/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx index 01cd6ccaf3..3a3a3e6b50 100644 --- a/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx index f8a2256055..1ec06b87d2 100644 --- a/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) diff --git a/calico-cloud_versioned_docs/version-23-2/operations/comms/index.mdx b/calico-cloud_versioned_docs/version-23-2/operations/comms/index.mdx index 5c0aeee98e..c4779edcc6 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/comms/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/comms/index.mdx @@ -49,14 +49,14 @@ The **Deployed to** column shows the namespace where the operator places the sec |---|---|---|---| | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `node-certs` | `typha-client` | `calico-system` | Installation/default | | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | | `typha-certs` | `typha-server` | `calico-system` | Installation/default | | `typha-certs-noncluster-host` | `typha-server-noncluster-host` | `calico-system` | Installation/default | diff --git a/calico-cloud_versioned_docs/version-23-2/operations/disconnect.mdx b/calico-cloud_versioned_docs/version-23-2/operations/disconnect.mdx index c63f8cdc8c..4b14e1a726 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/disconnect.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/disconnect.mdx @@ -48,7 +48,7 @@ not be successful. You will need to reach out to your support contact to create 1. Run the script and read the help to determine if you need to specify any flags `./downgrade.sh --help`. -1. Run the script with any needed flags, for example: `./downgrade.sh --remove-prometheus`. +1. Run the script with any needed flags, for example: `./downgrade.sh --remove-pickle`. ## Next steps diff --git a/calico-cloud_versioned_docs/version-23-2/operations/index.mdx b/calico-cloud_versioned_docs/version-23-2/operations/index.mdx index f8da8da396..3e97c60090 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/index.mdx @@ -18,11 +18,11 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring - + - - - + + + diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx index 74def9953e..0905c7faec 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -154,4 +154,4 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 842f83e06b..b5606f75db 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -29,11 +29,11 @@ The following example creates a Prometheus rule to monitor some important Fluent apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx index fc49d366a1..3e094a2aad 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx index 49b5fb329c..e94fa0f143 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Cloud connected cluster to route Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx index bfcc5039f5..09329ac659 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -306,11 +306,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -341,11 +341,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -358,7 +358,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -375,9 +375,9 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Port-forward the Prometheus pods and run this command with the forwarded port. diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx index b9b3579431..a91ef9ac47 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -32,10 +32,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -57,10 +57,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: tigera-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: tigera-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx index cde1d72c4e..e3dc07855d 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Cloud connected clusters ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,6 +14,6 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. - If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. + If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](byo-prometheus.mdx) +- [Bring your own Prometheus](byo-pickle.mdx) diff --git a/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx b/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx index c66b171c27..511c58de91 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx @@ -1426,8 +1426,8 @@ In the table below, you can look at the details of each project and license asso Tigera Proprietary - github.com/prometheus/client_golang/ - github.com/prometheus/client_golang/prometheus-v1.7.1 + github.com/pickle/client_golang/ + github.com/pickle/client_golang/pickle-v1.7.1 Apache 2.0 diff --git a/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx b/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx index c42646d765..bca2123a45 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). diff --git a/calico-cloud_versioned_docs/version-23-2/reference/index.mdx b/calico-cloud_versioned_docs/version-23-2/reference/index.mdx index 96baeba785..5f6d4e9f72 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/index.mdx @@ -65,10 +65,10 @@ APIs, CLI, architecture and design, and FAQ. - + - + ## Configuration on public clouds diff --git a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx index 12b94aa5c6..03f65ba63e 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx @@ -854,7 +854,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -949,7 +949,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1120,11 +1120,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2541,7 +2541,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2600,7 +2600,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3592,8 +3592,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4635,8 +4635,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5207,7 +5207,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5217,7 +5217,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5232,11 +5232,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5361,12 +5361,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-cloud_versioned_docs/version-23-2/reference/resources/kubecontrollersconfig.mdx b/calico-cloud_versioned_docs/version-23-2/reference/resources/kubecontrollersconfig.mdx index 512c8b5c18..a1f10978f3 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/resources/kubecontrollersconfig.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/resources/kubecontrollersconfig.mdx @@ -24,7 +24,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -64,7 +64,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-cloud_versioned_docs/version-23-2/releases.json b/calico-cloud_versioned_docs/version-23-2/releases.json index ce9c8cbf30..e59c08419c 100644 --- a/calico-cloud_versioned_docs/version-23-2/releases.json +++ b/calico-cloud_versioned_docs/version-23-2/releases.json @@ -166,29 +166,29 @@ "image": "tigera/packetcapture", "version": "v3.21.0-1.0" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "v3.21.0-1.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.43.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.62.0" }, "coreos-config-reloader": { "version": "v0.62.0" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "v3.21.0-1.0" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "v3.21.0-1.0" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "v3.21.0-1.0" }, "es-gateway": { diff --git a/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx b/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx index 3f0cf16d61..4a55693b8a 100644 --- a/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx +++ b/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-cloud_versioned_sidebars/version-22-2-sidebars.json b/calico-cloud_versioned_sidebars/version-22-2-sidebars.json index 400169744f..6a26005220 100644 --- a/calico-cloud_versioned_sidebars/version-22-2-sidebars.json +++ b/calico-cloud_versioned_sidebars/version-22-2-sidebars.json @@ -556,14 +556,14 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", + "operations/monitor/pickle/support", "operations/monitor/metrics/recommended-metrics", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -709,7 +709,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -730,7 +730,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] diff --git a/calico-cloud_versioned_sidebars/version-23-2-sidebars.json b/calico-cloud_versioned_sidebars/version-23-2-sidebars.json index 3c6ab7f058..d749c029e9 100644 --- a/calico-cloud_versioned_sidebars/version-23-2-sidebars.json +++ b/calico-cloud_versioned_sidebars/version-23-2-sidebars.json @@ -520,14 +520,14 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", + "operations/monitor/pickle/support", "operations/monitor/metrics/recommended-metrics", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -670,7 +670,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -691,7 +691,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] diff --git a/calico-enterprise/_includes/components/FelixConfig/config-params.json b/calico-enterprise/_includes/components/FelixConfig/config-params.json index 8f6cd44252..02ae543838 100644 --- a/calico-enterprise/_includes/components/FelixConfig/config-params.json +++ b/calico-enterprise/_includes/components/FelixConfig/config-params.json @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1216,7 +1216,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1243,7 +1243,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1270,7 +1270,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6036,7 +6036,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6063,7 +6063,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6090,7 +6090,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6117,7 +6117,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6144,7 +6144,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-enterprise/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js b/calico-enterprise/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js index c220becbf3..f0b20d07d6 100644 --- a/calico-enterprise/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js +++ b/calico-enterprise/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js @@ -149,7 +149,7 @@ EOF`} <> {`helm install calico-enterprise tigera/tigera-operator --version v0.0 \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

@@ -157,7 +157,7 @@ EOF`}

{`helm install calico-enterprise tigera/tigera-operator --version v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} @@ -168,7 +168,7 @@ EOF`} <> {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

@@ -176,7 +176,7 @@ EOF`}

{`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} diff --git a/calico-enterprise/_includes/components/InstallAKS.js b/calico-enterprise/_includes/components/InstallAKS.js index 0a909b39e6..f99e2da1c4 100644 --- a/calico-enterprise/_includes/components/InstallAKS.js +++ b/calico-enterprise/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise/_includes/components/InstallEKS.js b/calico-enterprise/_includes/components/InstallEKS.js index c971567072..6ee617a2f1 100644 --- a/calico-enterprise/_includes/components/InstallEKS.js +++ b/calico-enterprise/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise/_includes/components/InstallGKE.js b/calico-enterprise/_includes/components/InstallGKE.js index 11bfe1310b..5539e101b4 100644 --- a/calico-enterprise/_includes/components/InstallGKE.js +++ b/calico-enterprise/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise/_includes/components/InstallGeneric.js b/calico-enterprise/_includes/components/InstallGeneric.js index 62e7c87125..977f588d77 100644 --- a/calico-enterprise/_includes/components/InstallGeneric.js +++ b/calico-enterprise/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js index 003e6e431b..67168b5666 100644 --- a/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js @@ -8,7 +8,7 @@ import { prodname, baseUrl, filesUrl } from '../../variables'; export default function OpenShiftPrometheusOperator(props) { const createSecret = `oc create secret generic tigera-pull-secret \\ - --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\ + --type=kubernetes.io/dockerconfigjson -n tigera-pickle \\ --from-file=.dockerconfigjson=\n`; const notOSCodeBlock = props.upgradeFrom !== 'OpenSource' ? createSecret : ''; @@ -18,11 +18,11 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} ); } diff --git a/calico-enterprise/_includes/components/PrivateRegistryImagePath.js b/calico-enterprise/_includes/components/PrivateRegistryImagePath.js index 6a8c9e2882..5a6d7e1ec1 100644 --- a/calico-enterprise/_includes/components/PrivateRegistryImagePath.js +++ b/calico-enterprise/_includes/components/PrivateRegistryImagePath.js @@ -98,11 +98,11 @@ export default function PrivateRegistryImagePath() {

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */} diff --git a/calico-enterprise/_includes/components/PrivateRegistryRegular.js b/calico-enterprise/_includes/components/PrivateRegistryRegular.js index 872ff86272..a6088dced2 100644 --- a/calico-enterprise/_includes/components/PrivateRegistryRegular.js +++ b/calico-enterprise/_includes/components/PrivateRegistryRegular.js @@ -94,11 +94,11 @@ export default function PrivateRegistryRegular() { {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    diff --git a/calico-enterprise/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise/_includes/components/UpgradeOperatorSimple.js index 97d4f5deda..934b6b6487 100644 --- a/calico-enterprise/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml

  • @@ -80,7 +80,7 @@ export default function UpgradeOperatorSimple(props) {

  • If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now.

    - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml
    • diff --git a/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx index 5f2f05f16b..73db0eeb15 100644 --- a/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx b/calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx index dae22733ce..5c541c3808 100644 --- a/calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx @@ -103,7 +103,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator \ --create-namespace @@ -113,7 +113,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator \ --create-namespace diff --git a/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx index fcd5931fc4..10c59cd86d 100644 --- a/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise/getting-started/install-on-clusters/rancher.mdx index 9209e9ad2a..53c8fb1477 100644 --- a/calico-enterprise/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise/getting-started/install-on-clusters/rke2.mdx index 1555d904a6..f53e85ef00 100644 --- a/calico-enterprise/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/manifest-archive.mdx b/calico-enterprise/getting-started/manifest-archive.mdx index a252269932..a42ecc985d 100644 --- a/calico-enterprise/getting-started/manifest-archive.mdx +++ b/calico-enterprise/getting-started/manifest-archive.mdx @@ -48,7 +48,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. diff --git a/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 51dcbb131c..6ee8ea4480 100644 --- a/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -60,7 +60,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -69,7 +69,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -84,12 +84,12 @@ The following steps assume the Calico deployment is installed on `tigera-operato {'$[version]' === 'master' ? ( `helm upgrade calico tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) : ( `helm upgrade calico tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) } diff --git a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index ecdbce591b..eda9a700ce 100644 --- a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -91,7 +91,7 @@ The `tigera-operator` chart does not contain the $[prodname] CRDs, since Helm do ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -100,7 +100,7 @@ The `tigera-operator` chart does not contain the $[prodname] CRDs, since Helm do ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -161,13 +161,13 @@ The `tigera-operator` chart does not contain the $[prodname] CRDs, since Helm do {'$[version]' === 'master' ? ( `helm upgrade calico-enterprise --values= tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) : ( `helm upgrade calico-enterprise --values= tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) diff --git a/calico-enterprise/multicluster/federation/kubeconfig.mdx b/calico-enterprise/multicluster/federation/kubeconfig.mdx index 3f33c16d74..04c12d884c 100644 --- a/calico-enterprise/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx index fa5c7a0587..23054fabf8 100644 --- a/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx +++ b/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx @@ -133,13 +133,13 @@ To install a $[prodname] [managed](../standard-install/create-a-managed-cluster# {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator \\ diff --git a/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx index 4756c0472a..05a17261ec 100644 --- a/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx +++ b/calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx @@ -153,12 +153,12 @@ To install a $[prodname] [management](create-a-management-cluster-helm#value) cl {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace`} @@ -249,12 +249,12 @@ For example, if you are using EKS, you must meet the requirements defined in [cr {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace`} diff --git a/calico-enterprise/network-policy/beginners/simple-policy-cnx.mdx b/calico-enterprise/network-policy/beginners/simple-policy-cnx.mdx index c8581977f2..6714c720b7 100644 --- a/calico-enterprise/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-enterprise/network-policy/beginners/simple-policy-cnx.mdx @@ -92,15 +92,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -118,7 +118,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx b/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx index 88ff7dd86b..c3579b10e8 100644 --- a/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx index 1bedcc63bd..2081bb65c8 100644 --- a/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) diff --git a/calico-enterprise/observability/review-unused-network-policies.mdx b/calico-enterprise/observability/review-unused-network-policies.mdx index 69c22e2483..4126608ad8 100644 --- a/calico-enterprise/observability/review-unused-network-policies.mdx +++ b/calico-enterprise/observability/review-unused-network-policies.mdx @@ -71,7 +71,7 @@ WARNING: Some unused policies have been recently edited! Unused Policies since 2026-01-14T00:00:00Z (7) KIND NAMESPACE NAME PREV GENS EVALUATED RECENTLY EDITED NetworkPolicy calico-system calico-system.default-deny Yes No -NetworkPolicy tigera-prometheus calico-system.default-deny No No +NetworkPolicy tigera-pickle calico-system.default-deny No No GlobalNetworkPolicy N/A anp-v2 No No KubernetesNetworkPolicy test-policies k8snp-v2 Yes Yes StagedKubernetesNetworkPolicy test-policies sknp-v2 Yes No @@ -121,7 +121,7 @@ $ calicoctl review unused-policies -o json { "kind": "NetworkPolicy", "name": "calico-system.default-deny", - "namespace": "tigera-prometheus", + "namespace": "tigera-pickle", "generation": 1, "creationTimestamp": "2026-04-21T16:26:00Z", "lastUpdate": "2026-04-21T16:26:00Z", diff --git a/calico-enterprise/operations/comms/index.mdx b/calico-enterprise/operations/comms/index.mdx index c7275dbc71..4d69b1f28c 100644 --- a/calico-enterprise/operations/comms/index.mdx +++ b/calico-enterprise/operations/comms/index.mdx @@ -50,9 +50,9 @@ The **Deployed to** column shows the namespace where the operator places the sec |---|---|---|---| | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `internal-manager-tls` | `calico-manager` | `calico-system` | Manager/tigera-secure | | `intrusion-detection-tls` | `intrusion-detection-tls` | `tigera-intrusion-detection` | IntrusionDetection/tigera-secure | @@ -61,8 +61,8 @@ The **Deployed to** column shows the namespace where the operator places the sec | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `policy-recommendation-tls` | `policy-recommendation-tls` | `calico-system` | PolicyRecommendation/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | -| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-prometheus` | Monitor/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-pickle` | Monitor/tigera-secure | | `tigera-secure-elasticsearch-cert` | `tigera-secure-es-gateway-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-internal-elasticsearch-cert` | `tigera-secure-es-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-kibana-cert` | `tigera-secure-kb-http` | `tigera-kibana` | LogStorage/tigera-secure | diff --git a/calico-enterprise/operations/index.mdx b/calico-enterprise/operations/index.mdx index 50185d43f2..222f8dbce8 100644 --- a/calico-enterprise/operations/index.mdx +++ b/calico-enterprise/operations/index.mdx @@ -46,10 +46,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise/operations/license-options.mdx b/calico-enterprise/operations/license-options.mdx index 30579f20d1..8a5cd015c0 100644 --- a/calico-enterprise/operations/license-options.mdx +++ b/calico-enterprise/operations/license-options.mdx @@ -73,7 +73,7 @@ These metrics are scraped by the built-in Prometheus instance via the `tigera-op $[prodname] installs PrometheusRule resources with alerting rules for license expiration. You can view them with: ```bash -kubectl -n tigera-prometheus get prometheusrule calico -o yaml +kubectl -n tigera-pickle get picklerule calico -o yaml ``` The built-in rules include: @@ -81,10 +81,10 @@ The built-in rules include: - **LicenseExpiringWarning**: fires when the license expires in less than 30 days - **LicenseExpiringCritical**: fires when the license expires in less than 7 days, or is invalid -To route these alerts, see [Configure Alertmanager](monitor/prometheus/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](monitor/pickle/alertmanager.mdx). ## Additional resources - [LicenseKey resource](../reference/resources/licensekey.mdx) -- [Configure Alertmanager](monitor/prometheus/alertmanager.mdx) -- [Configure Prometheus](monitor/prometheus/configure-prometheus.mdx) +- [Configure Alertmanager](monitor/pickle/alertmanager.mdx) +- [Configure Prometheus](monitor/pickle/configure-pickle.mdx) diff --git a/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx index c33bad7fb1..61bf089dc9 100644 --- a/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -164,4 +164,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index b15bab97eb..1c2be4cb28 100644 --- a/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch @@ -50,11 +50,11 @@ rules. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-storage-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-elasticsearch.rules @@ -132,11 +132,11 @@ have crossed certain thresholds: apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx b/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx index 645a2952b7..dc471492dc 100644 --- a/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx @@ -107,7 +107,7 @@ The `tigera_operator_tls_certificate_expiry_timestamp_seconds` metric reports th $[prodname] installs a PrometheusRule resource named `calico` with alerting rules that use these metrics. You can view it with: ```bash -kubectl -n tigera-prometheus get prometheusrule calico -o yaml +kubectl -n tigera-pickle get picklerule calico -o yaml ``` The built-in rules include: @@ -124,10 +124,10 @@ The built-in rules include: | `ComponentProgressingWarning` | Component progressing for > 15m | warning | | `ComponentProgressingCritical` | Component progressing for > 30m | critical | -To route these alerts, see [Configure Alertmanager](../prometheus/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](../pickle/alertmanager.mdx). ## Additional resources - [License expiration and renewal](../../license-options.mdx) -- [Configure Prometheus](../prometheus/configure-prometheus.mdx) -- [BYO Prometheus](../prometheus/byo-prometheus.mdx) +- [Configure Prometheus](../pickle/configure-pickle.mdx) +- [BYO Prometheus](../pickle/byo-pickle.mdx) diff --git a/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx index 8297fa724a..2a04c6830c 100644 --- a/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx index c31446657e..1534f898a9 100644 --- a/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx index 8e46b69f5a..f9db9884e8 100644 --- a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx @@ -27,13 +27,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -42,7 +42,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -53,10 +53,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -68,14 +68,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -91,18 +91,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -114,11 +114,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -132,18 +132,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -155,11 +155,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -173,18 +173,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -196,11 +196,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -214,18 +214,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -237,11 +237,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -258,7 +258,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -269,7 +269,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -307,11 +307,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -342,11 +342,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -360,18 +360,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -383,11 +383,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/operator-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/operator-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -400,7 +400,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -417,8 +417,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx index ce12058105..ba84d577af 100644 --- a/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -32,10 +32,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -57,10 +57,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: calico-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: calico-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-enterprise/operations/monitor/prometheus/support.mdx b/calico-enterprise/operations/monitor/prometheus/support.mdx index 06e2017734..4784b3a6bb 100644 --- a/calico-enterprise/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,7 +14,7 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. #### Prometheus on $[prodnameWindows] @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-prometheus.mdx). +For details, see [Bring your own Prometheus](byo-pickle.mdx). diff --git a/calico-enterprise/reference/architecture/overview.mdx b/calico-enterprise/reference/architecture/overview.mdx index 3da4e4cd8b..42fa1566d9 100644 --- a/calico-enterprise/reference/architecture/overview.mdx +++ b/calico-enterprise/reference/architecture/overview.mdx @@ -29,13 +29,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components @@ -109,7 +109,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise/reference/clis/calicoctl/cluster/diags.mdx b/calico-enterprise/reference/clis/calicoctl/cluster/diags.mdx index af93e03ba4..43dc2c8364 100644 --- a/calico-enterprise/reference/clis/calicoctl/cluster/diags.mdx +++ b/calico-enterprise/reference/clis/calicoctl/cluster/diags.mdx @@ -349,11 +349,11 @@ Collecting detailed diags for pod tigera-packetcapture-758ff8c7db-slmd7 in names Collecting diags for pod: tigera-packetcapture-758ff8c7db-slmd7 Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting detailed diags for namespace tigera-pickle... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... ==== Producing a diagnostics bundle. ==== diff --git a/calico-enterprise/reference/clis/calicoq/host.mdx b/calico-enterprise/reference/clis/calicoq/host.mdx index dd86ff9088..8755053dab 100644 --- a/calico-enterprise/reference/clis/calicoq/host.mdx +++ b/calico-enterprise/reference/clis/calicoq/host.mdx @@ -35,10 +35,10 @@ Sample output follows. ``` Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 Policies: diff --git a/calico-enterprise/reference/component-resources/configure-resources.mdx b/calico-enterprise/reference/component-resources/configure-resources.mdx index 606294ae87..afaedd8ab0 100644 --- a/calico-enterprise/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise/reference/component-resources/configure-resources.mdx @@ -910,10 +910,10 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -922,7 +922,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -933,7 +933,7 @@ The "config-reloader" container has default resource values set based by the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { "limits": { "cpu": "500m", @@ -975,7 +975,7 @@ The "config-reloader" container has default resource values set based by the Pro ### Alertmanager -To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -987,7 +987,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. diff --git a/calico-enterprise/reference/component-resources/kube-controllers/index.mdx b/calico-enterprise/reference/component-resources/kube-controllers/index.mdx index bd9849c941..dad7a2f144 100644 --- a/calico-enterprise/reference/component-resources/kube-controllers/index.mdx +++ b/calico-enterprise/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index 943cd61444..3207e1c9a8 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -866,7 +866,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -963,7 +963,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1251,11 +1251,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2188,7 +2188,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2217,7 +2217,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2278,7 +2278,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3285,8 +3285,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4530,8 +4530,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertmanager` _[Alertmanager](#alertmanager)_ | (Optional) Alertmanager is the configuration for the Alertmanager. | @@ -5184,7 +5184,7 @@ _Appears in:_ - [ManagerDeploymentContainer](#managerdeploymentcontainer) - [PacketCaptureAPIDeploymentContainer](#packetcaptureapideploymentcontainer) - [PolicyRecommendationDeploymentContainer](#policyrecommendationdeploymentcontainer) -- [PrometheusContainer](#prometheuscontainer) +- [PrometheusContainer](#picklecontainer) - [TyphaDeploymentContainer](#typhadeploymentcontainer) - [WhiskerDeploymentContainer](#whiskerdeploymentcontainer) @@ -5222,7 +5222,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5232,7 +5232,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5249,11 +5249,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5378,12 +5378,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-enterprise/reference/resources/kubecontrollersconfig.mdx b/calico-enterprise/reference/resources/kubecontrollersconfig.mdx index e382dd4681..43686e2498 100644 --- a/calico-enterprise/reference/resources/kubecontrollersconfig.mdx +++ b/calico-enterprise/reference/resources/kubecontrollersconfig.mdx @@ -24,7 +24,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -63,7 +63,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-enterprise/releases.json b/calico-enterprise/releases.json index 9a65bcfea4..016358895e 100644 --- a/calico-enterprise/releases.json +++ b/calico-enterprise/releases.json @@ -162,26 +162,26 @@ "image": "tigera/packetcapture", "version": "master" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "master" }, "upstream-istio": { "version": "1.28.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.48.1" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "master" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "master" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "master" }, "es-gateway": { diff --git a/calico-enterprise/threat/configuring-webhooks.mdx b/calico-enterprise/threat/configuring-webhooks.mdx index 01b05b33ca..b5d76bb09b 100644 --- a/calico-enterprise/threat/configuring-webhooks.mdx +++ b/calico-enterprise/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js index c220becbf3..f0b20d07d6 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js @@ -149,7 +149,7 @@ EOF`} <> {`helm install calico-enterprise tigera/tigera-operator --version v0.0 \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -157,7 +157,7 @@ EOF`}

    {`helm install calico-enterprise tigera/tigera-operator --version v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} @@ -168,7 +168,7 @@ EOF`} <> {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -176,7 +176,7 @@ EOF`}

    {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js index d23b6ec54d..eeeb711465 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js @@ -31,7 +31,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -141,7 +141,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js index afbd134d46..41d89d0eec 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js @@ -33,7 +33,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -192,7 +192,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js index 89ebe93449..f9cb1a3604 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js @@ -32,7 +32,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js index 5d4ef1de9c..7da879bf77 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js @@ -37,7 +37,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js index 003e6e431b..67168b5666 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js @@ -8,7 +8,7 @@ import { prodname, baseUrl, filesUrl } from '../../variables'; export default function OpenShiftPrometheusOperator(props) { const createSecret = `oc create secret generic tigera-pull-secret \\ - --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\ + --type=kubernetes.io/dockerconfigjson -n tigera-pickle \\ --from-file=.dockerconfigjson=\n`; const notOSCodeBlock = props.upgradeFrom !== 'OpenSource' ? createSecret : ''; @@ -18,11 +18,11 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryImagePath.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryImagePath.js index 43a125024d..9506ff85cb 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryImagePath.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryImagePath.js @@ -98,11 +98,11 @@ export default function PrivateRegistryImagePath() {

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */} diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryRegular.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryRegular.js index d12ee6e426..cfb71665f2 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryRegular.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/PrivateRegistryRegular.js @@ -94,11 +94,11 @@ export default function PrivateRegistryRegular() { {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js index 55e61e56b1..81cfff6ba7 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml

  • @@ -80,7 +80,7 @@ export default function UpgradeOperatorSimple(props) {

  • If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now.

    - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml
    • diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx index c9b65e1bda..ccf35e799b 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -82,7 +82,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/helm.mdx index a10be72ac5..28ce88df76 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/helm.mdx @@ -96,7 +96,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator --create-namespace ``` @@ -105,7 +105,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator --create-namespace ``` diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index c9ab5c70ed..50b9d4902f 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -102,7 +102,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx index c4fa4047cf..3174275da7 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx @@ -70,7 +70,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx index bc24244e1c..1b16aadabc 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx @@ -67,7 +67,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/manifest-archive.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/manifest-archive.mdx index 62499c2396..5005de2a21 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/manifest-archive.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/manifest-archive.mdx @@ -47,7 +47,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 38e3c520c8..5c0968d93b 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -37,7 +37,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -49,12 +49,12 @@ The following steps assume the Calico deployment is installed on `tigera-operato {'$[version]' === 'master' ? ( `helm upgrade calico tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) : ( `helm upgrade calico tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) } diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index e4ddff270d..331baed40f 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -134,13 +134,13 @@ These steps differ based on your cluster type. If you are unsure of your cluster {'$[version]' === 'master' ? ( `helm upgrade calico-enterprise --values= tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) : ( `helm upgrade calico-enterprise --values= tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) diff --git a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx index a7f3daaa8d..98f34519b3 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx @@ -338,7 +338,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx index dd6c5cd6be..cb99ba9293 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx @@ -126,12 +126,12 @@ To install a $[prodname] [managed](../standard-install/create-a-managed-cluster# {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx index d669ec33f6..9e698deaf3 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx @@ -145,11 +145,11 @@ To install a $[prodname] [management](create-a-management-cluster-helm#value) cl {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace`} @@ -233,11 +233,11 @@ For example, if you are using EKS, you must meet the requirements defined in [cr {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/simple-policy-cnx.mdx b/calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/simple-policy-cnx.mdx index f685ebae4b..36fecdb66b 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/simple-policy-cnx.mdx @@ -92,15 +92,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -118,7 +118,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/comms/secure-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/comms/secure-metrics.mdx index 3790f95c77..c4209c168b 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/comms/secure-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx index adcc11f46d..7053f79df6 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx @@ -56,10 +56,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx index 96c2d216b5..44d219767d 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -165,4 +165,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index bc9e34ec01..5dd1ca8f77 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch @@ -50,11 +50,11 @@ rules. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-storage-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-elasticsearch.rules @@ -132,11 +132,11 @@ have crossed certain thresholds: apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx index 33dc93e739..7bc8f8d951 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx @@ -33,7 +33,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) ### Add license agent in your Kubernetes cluster @@ -62,11 +62,11 @@ In the following example, an alert is configured when the license expiry is fewe apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-license - namespace: tigera-prometheus + name: calico-pickle-license + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-license.rules @@ -89,4 +89,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../prometheus/alertmanager.mdx) +- [Configure Alertmanager](../pickle/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx index 9a7afc6f47..d9d01f1904 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx index 702496097b..dcd8f3a73c 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager, a Prometheus feature that routes alerts. Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx index aae414e814..c339157ab8 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **Create a service to expose Felix metrics** @@ -324,11 +324,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -359,11 +359,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -376,7 +376,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -393,8 +393,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx index de68da887c..3f97261b95 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -31,11 +31,11 @@ As an example, the range query in this Manifest is 10 seconds. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -56,11 +56,11 @@ To update this alerting rule, to say, execute the query with a range of apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: tigera-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: tigera-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx index b4eae628b4..cd20ac7b61 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Prometheus support in Calico Enterprise. ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,7 +14,7 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. #### Prometheus on $[prodnameWindows] @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-prometheus.mdx). +For details, see [Bring your own Prometheus](byo-pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx index 81c740d0f3..6e19f0469d 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoctl/cluster/diags.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoctl/cluster/diags.mdx index ab36c4effe..06dfbdcc77 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoctl/cluster/diags.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoctl/cluster/diags.mdx @@ -342,11 +342,11 @@ Collecting detailed diags for pod tigera-packetcapture-758ff8c7db-slmd7 in names Collecting diags for pod: tigera-packetcapture-758ff8c7db-slmd7 Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting detailed diags for namespace tigera-pickle... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... Collecting detailed diags for namespace tigera-system... Collecting detailed diags for pod tigera-apiserver-6f5ddf5697-6qfgj in namespace tigera-system on node ip-172-16-101-171.us-west-2.compute.internal... diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoq/host.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoq/host.mdx index c784301419..7e8b9fefcb 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoq/host.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/clis/calicoq/host.mdx @@ -35,10 +35,10 @@ Sample output follows. ``` Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 Policies: diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx index d7c7b367b7..ca9384f07f 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx @@ -910,10 +910,10 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -922,7 +922,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -933,7 +933,7 @@ The "config-reloader" container has default resource values set based by the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { "limits": { "cpu": "500m", @@ -975,7 +975,7 @@ The "config-reloader" container has default resource values set based by the Pro ### Alertmanager -To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -987,7 +987,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx index e6dea5d9fd..bda7643bff 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx @@ -752,7 +752,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -845,7 +845,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1016,11 +1016,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2408,7 +2408,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2437,7 +2437,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2496,7 +2496,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -2869,8 +2869,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -3857,8 +3857,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -4397,7 +4397,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -4407,7 +4407,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -4422,11 +4422,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -4520,12 +4520,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/felixconfig.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/felixconfig.mdx index 600215e7c3..fe43839d24 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/felixconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/felixconfig.mdx @@ -87,13 +87,13 @@ spec: | metadataPort | The port of the metadata server. This, combined with global.MetadataAddr (if not 'None'), is used to set up a NAT rule, from 169.254.169.254:80 to MetadataAddr:MetadataPort. In most cases this should not need to be changed. | int | int | `8775` | | natOutgoingAddress | The source address to use for outgoing NAT. By default an iptables MASQUERADE rule determines the source address which will use the address on the host interface the traffic leaves on. | IPV4 | string | `""` | | policySyncPathPrefix | File system path where Felix notifies services of policy changes over Unix domain sockets. This is required only if you're configuring [L7 logs](../../observability/elastic/l7/configure.mdx), or [egress gateways](../../networking/egress/index.mdx). Set to `""` to disable. | string | string | `""` | -| prometheusGoMetricsEnabled | Set to `false` to disable Go runtime metrics collection, which the Prometheus client does by default. This reduces the number of metrics reported, reducing Prometheus load. | boolean | boolean | `true` | -| prometheusMetricsEnabled | Set to `true` to enable the experimental Prometheus metrics server in Felix. | boolean | boolean | `false` | -| prometheusMetricsHost | TCP network address that the Prometheus metrics server should bind to. | IPv4, IPv6, Hostname | string | `""` | -| prometheusMetricsPort | TCP port that the Prometheus metrics server should bind to. | int | int | `9091` | -| prometheusProcessMetricsEnabled | Set to `false` to disable process metrics collection, which the Prometheus client does by default. This reduces the number of metrics reported, reducing Prometheus load. | boolean | boolean | `true` | -| prometheusReporterEnabled | Set to `true` to enable configure Felix to keep count of recently denied packets and publish these as Prometheus metrics. Note that denied packet metrics are independent of the `dropActionOverride` setting. Specifically, if packets that would normally be denied are being allowed through by a setting of `Accept` or `LogAndAccept`, those packets still get counted as denied packets. | `true`, `false` | boolean | `false` | -| prometheusReporterPort | The TCP port on which to report denied packet metrics, if `prometheusReporterEnabled` is set to `true`. | | | `9092` | +| pickleGoMetricsEnabled | Set to `false` to disable Go runtime metrics collection, which the Prometheus client does by default. This reduces the number of metrics reported, reducing Prometheus load. | boolean | boolean | `true` | +| pickleMetricsEnabled | Set to `true` to enable the experimental Prometheus metrics server in Felix. | boolean | boolean | `false` | +| pickleMetricsHost | TCP network address that the Prometheus metrics server should bind to. | IPv4, IPv6, Hostname | string | `""` | +| pickleMetricsPort | TCP port that the Prometheus metrics server should bind to. | int | int | `9091` | +| pickleProcessMetricsEnabled | Set to `false` to disable process metrics collection, which the Prometheus client does by default. This reduces the number of metrics reported, reducing Prometheus load. | boolean | boolean | `true` | +| pickleReporterEnabled | Set to `true` to enable configure Felix to keep count of recently denied packets and publish these as Prometheus metrics. Note that denied packet metrics are independent of the `dropActionOverride` setting. Specifically, if packets that would normally be denied are being allowed through by a setting of `Accept` or `LogAndAccept`, those packets still get counted as denied packets. | `true`, `false` | boolean | `false` | +| pickleReporterPort | The TCP port on which to report denied packet metrics, if `pickleReporterEnabled` is set to `true`. | | | `9092` | | removeExternalRoutes | Whether or not to remove device routes that have not been programmed by Felix. Disabling this will allow external applications to also add device routes. | bool | boolean | `true` | | reportingInterval | Interval at which Felix reports its status into the datastore. 0 means disabled and is correct for Kubernetes-only clusters. Must be non-zero in OpenStack deployments. | `5s`, `10s`, `1m` etc. | duration | `30s` | | reportingTTL | Time-to-live setting for process-wide status reports. | `5s`, `10s`, `1m` etc. | duration | `90s` | diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/kubecontrollersconfig.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/kubecontrollersconfig.mdx index e6ba483ee5..37872c96f8 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/kubecontrollersconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/resources/kubecontrollersconfig.mdx @@ -16,7 +16,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -42,7 +42,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-enterprise_versioned_docs/version-3.20-2/release-notes/index.mdx b/calico-enterprise_versioned_docs/version-3.20-2/release-notes/index.mdx index da21b944be..fd84eb6106 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/release-notes/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/release-notes/index.mdx @@ -293,7 +293,7 @@ October 21, 2025 * ***Breaking change***: This release fixes the defaulting behaviour for `Authentication.Spec.OIDC.requestedScopes` such that it now includes `offline_access` as documented in the API. In the unlikely case that your identity provider does not support `offline_access` and if you did previously not specify `requestedScopes`, you should set `requestedScopes` to `[profile, openid, email]`. * Fixes an issue that prevented the UI from renewing session tokens when using LDAP. -* Avoid writing 0 or negative values to prometheus from linseed, leading to recoverable panics in the logs. +* Avoid writing 0 or negative values to pickle from linseed, leading to recoverable panics in the logs. * Fix logic for wrapping IP addresses in square brackets to only wrap IPv6 addresses. #### Known issues diff --git a/calico-enterprise_versioned_docs/version-3.20-2/releases.json b/calico-enterprise_versioned_docs/version-3.20-2/releases.json index 95e1f9b4b9..a838fb019f 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/releases.json +++ b/calico-enterprise_versioned_docs/version-3.20-2/releases.json @@ -76,10 +76,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -207,17 +207,17 @@ "version": "v3.20.7", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.20.7", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.20.7", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.20.7", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.20.7", @@ -227,9 +227,9 @@ "version": "v3.20.7", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.20.7", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.20.7", @@ -325,10 +325,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -456,17 +456,17 @@ "version": "v3.20.6", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.20.6", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.20.6", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.20.6", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.20.6", @@ -476,9 +476,9 @@ "version": "v3.20.6", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.20.6", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.20.6", @@ -574,10 +574,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -705,17 +705,17 @@ "version": "v3.20.5", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.20.5", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.20.5", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.20.5", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.20.5", @@ -725,9 +725,9 @@ "version": "v3.20.5", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.20.5", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.20.5", @@ -820,10 +820,10 @@ "coreos-config-reloader": { "version": "v0.76.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -951,17 +951,17 @@ "version": "v3.20.4", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.20.4", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.20.4", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.20.4", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.20.4", @@ -971,9 +971,9 @@ "version": "v3.20.4", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.20.4", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.20.4", @@ -1069,10 +1069,10 @@ "coreos-config-reloader": { "version": "v0.76.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.54.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.0" }, "csi": { @@ -1200,17 +1200,17 @@ "version": "v3.20.3", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.20.3", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.20.3", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.20.3", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.20.3", @@ -1220,9 +1220,9 @@ "version": "v3.20.3", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.20.3", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.20.3", @@ -1318,10 +1318,10 @@ "coreos-config-reloader": { "version": "v0.76.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.54.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.0" }, "csi": { @@ -1449,17 +1449,17 @@ "version": "v3.20.2", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.20.2", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.20.2", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.20.2", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.20.2", @@ -1469,9 +1469,9 @@ "version": "v3.20.2", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.20.2", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.20.2", @@ -1665,29 +1665,29 @@ "image": "tigera/policy-recommendation", "version": "v3.20.1" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "v3.20.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.54.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.0" }, "coreos-config-reloader": { "version": "v0.76.0" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "v3.20.1" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "v3.20.1" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "v3.20.1" }, "es-gateway": { @@ -1924,29 +1924,29 @@ "image": "tigera/policy-recommendation", "version": "v3.20.0-2.2" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "v3.20.0-2.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.48.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.73.2" }, "coreos-config-reloader": { "version": "v0.73.2" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "v3.20.0-2.2" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "v3.20.0-2.2" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "v3.20.0-2.2" }, "es-gateway": { @@ -2183,29 +2183,29 @@ "image": "tigera/policy-recommendation", "version": "v3.20.0-2.0" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "v3.20.0-2.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.48.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.73.2" }, "coreos-config-reloader": { "version": "v0.73.2" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "v3.20.0-2.0" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "v3.20.0-2.0" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "v3.20.0-2.0" }, "es-gateway": { @@ -2438,29 +2438,29 @@ "image": "tigera/policy-recommendation", "version": "v3.20.0-1.0" }, - "prometheus": { - "image": "tigera/prometheus", + "pickle": { + "image": "tigera/pickle", "version": "v3.20.0-1.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.48.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.73.2" }, "coreos-config-reloader": { "version": "v0.73.2" }, - "prometheus-operator": { - "image": "tigera/prometheus-operator", + "pickle-operator": { + "image": "tigera/pickle-operator", "version": "v3.20.0-1.0" }, - "prometheus-config-reloader": { - "image": "tigera/prometheus-config-reloader", + "pickle-config-reloader": { + "image": "tigera/pickle-config-reloader", "version": "v3.20.0-1.0" }, - "tigera-prometheus-service": { - "image": "tigera/prometheus-service", + "tigera-pickle-service": { + "image": "tigera/pickle-service", "version": "v3.20.0-1.0" }, "es-gateway": { diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/FelixConfig/config-params.json b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/FelixConfig/config-params.json index 0b129efe0f..397e6ca65a 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/FelixConfig/config-params.json +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/FelixConfig/config-params.json @@ -970,7 +970,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -997,7 +997,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1024,7 +1024,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1051,7 +1051,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1078,7 +1078,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1105,7 +1105,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1132,7 +1132,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1159,7 +1159,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1186,7 +1186,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -5395,7 +5395,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5422,7 +5422,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5449,7 +5449,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -5476,7 +5476,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5503,7 +5503,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js index c220becbf3..f0b20d07d6 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js @@ -149,7 +149,7 @@ EOF`} <> {`helm install calico-enterprise tigera/tigera-operator --version v0.0 \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -157,7 +157,7 @@ EOF`}

    {`helm install calico-enterprise tigera/tigera-operator --version v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} @@ -168,7 +168,7 @@ EOF`} <> {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -176,7 +176,7 @@ EOF`}

    {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js index 5fcb9cdb44..cdd1bcc48b 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js index 825927ad3c..afb6e89b33 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js index d08a015030..82478d4c9d 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js index 9b6180bee7..5d17b47c83 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js index 003e6e431b..67168b5666 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js @@ -8,7 +8,7 @@ import { prodname, baseUrl, filesUrl } from '../../variables'; export default function OpenShiftPrometheusOperator(props) { const createSecret = `oc create secret generic tigera-pull-secret \\ - --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\ + --type=kubernetes.io/dockerconfigjson -n tigera-pickle \\ --from-file=.dockerconfigjson=\n`; const notOSCodeBlock = props.upgradeFrom !== 'OpenSource' ? createSecret : ''; @@ -18,11 +18,11 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryImagePath.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryImagePath.js index 43a125024d..9506ff85cb 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryImagePath.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryImagePath.js @@ -98,11 +98,11 @@ export default function PrivateRegistryImagePath() {

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */} diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryRegular.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryRegular.js index d12ee6e426..cfb71665f2 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryRegular.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/PrivateRegistryRegular.js @@ -94,11 +94,11 @@ export default function PrivateRegistryRegular() { {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js index 55e61e56b1..81cfff6ba7 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml

  • @@ -80,7 +80,7 @@ export default function UpgradeOperatorSimple(props) {

  • If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now.

    - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml
    • diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx index 16e959837c..dfbba79a40 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/helm.mdx index a10be72ac5..28ce88df76 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/helm.mdx @@ -96,7 +96,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator --create-namespace ``` @@ -105,7 +105,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator --create-namespace ``` diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 9ec8df81cc..6fa6c671a5 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx index 12d9dce3b2..1e2e4f3f9a 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx index c00c061dfa..0ee98fd119 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/manifest-archive.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/manifest-archive.mdx index 89bd31dd0a..de26537123 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/manifest-archive.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/manifest-archive.mdx @@ -48,7 +48,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 47546923b8..62fc10299f 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -47,7 +47,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -59,12 +59,12 @@ The following steps assume the Calico deployment is installed on `tigera-operato {'$[version]' === 'master' ? ( `helm upgrade calico tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) : ( `helm upgrade calico tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) } diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index fce7e189ae..aba23727cc 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -134,13 +134,13 @@ These steps differ based on your cluster type. If you are unsure of your cluster {'$[version]' === 'master' ? ( `helm upgrade calico-enterprise --values= tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) : ( `helm upgrade calico-enterprise --values= tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) diff --git a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx index f7e99ce537..9c1cd02208 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx index dd6c5cd6be..cb99ba9293 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx @@ -126,12 +126,12 @@ To install a $[prodname] [managed](../standard-install/create-a-managed-cluster# {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx index d669ec33f6..9e698deaf3 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx @@ -145,11 +145,11 @@ To install a $[prodname] [management](create-a-management-cluster-helm#value) cl {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace`} @@ -233,11 +233,11 @@ For example, if you are using EKS, you must meet the requirements defined in [cr {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.21-2/network-policy/beginners/simple-policy-cnx.mdx b/calico-enterprise_versioned_docs/version-3.21-2/network-policy/beginners/simple-policy-cnx.mdx index f685ebae4b..36fecdb66b 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/network-policy/beginners/simple-policy-cnx.mdx @@ -92,15 +92,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -118,7 +118,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/comms/secure-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/comms/secure-metrics.mdx index 3790f95c77..c4209c168b 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/comms/secure-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx index adcc11f46d..7053f79df6 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx @@ -56,10 +56,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx index 96c2d216b5..44d219767d 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -165,4 +165,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index bc9e34ec01..5dd1ca8f77 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch @@ -50,11 +50,11 @@ rules. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-storage-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-elasticsearch.rules @@ -132,11 +132,11 @@ have crossed certain thresholds: apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx index 630b0742c1..45003ae6f2 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx @@ -33,7 +33,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) ### Add license agent in your Kubernetes cluster @@ -62,11 +62,11 @@ In the following example, an alert is configured when the license expiry is fewe apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-license - namespace: tigera-prometheus + name: calico-pickle-license + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-license.rules @@ -89,4 +89,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../prometheus/alertmanager.mdx) +- [Configure Alertmanager](../pickle/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx index b0fb0d5fdd..e331a72722 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx index 702496097b..dcd8f3a73c 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager, a Prometheus feature that routes alerts. Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx index 2f90f79daf..68cffa4008 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -306,11 +306,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -341,11 +341,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -358,7 +358,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -375,8 +375,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx index de68da887c..3f97261b95 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -31,11 +31,11 @@ As an example, the range query in this Manifest is 10 seconds. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -56,11 +56,11 @@ To update this alerting rule, to say, execute the query with a range of apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: tigera-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: tigera-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx index b4eae628b4..cd20ac7b61 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Prometheus support in Calico Enterprise. ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,7 +14,7 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. #### Prometheus on $[prodnameWindows] @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-prometheus.mdx). +For details, see [Bring your own Prometheus](byo-pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx index 329cfdf22e..f8dd40946c 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoctl/cluster/diags.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoctl/cluster/diags.mdx index ab36c4effe..06dfbdcc77 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoctl/cluster/diags.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoctl/cluster/diags.mdx @@ -342,11 +342,11 @@ Collecting detailed diags for pod tigera-packetcapture-758ff8c7db-slmd7 in names Collecting diags for pod: tigera-packetcapture-758ff8c7db-slmd7 Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting detailed diags for namespace tigera-pickle... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... Collecting detailed diags for namespace tigera-system... Collecting detailed diags for pod tigera-apiserver-6f5ddf5697-6qfgj in namespace tigera-system on node ip-172-16-101-171.us-west-2.compute.internal... diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoq/host.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoq/host.mdx index c784301419..7e8b9fefcb 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoq/host.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/clis/calicoq/host.mdx @@ -35,10 +35,10 @@ Sample output follows. ``` Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 Policies: diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx index 90457c4973..2629bf481d 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx @@ -910,10 +910,10 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -922,7 +922,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -933,7 +933,7 @@ The "config-reloader" container has default resource values set based by the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { "limits": { "cpu": "500m", @@ -975,7 +975,7 @@ The "config-reloader" container has default resource values set based by the Pro ### Alertmanager -To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -987,7 +987,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx index 5cdbbb09c4..e45aff6298 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx @@ -820,7 +820,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -913,7 +913,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1084,11 +1084,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2476,7 +2476,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2505,7 +2505,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2564,7 +2564,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3446,8 +3446,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4470,8 +4470,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5026,7 +5026,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5036,7 +5036,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5051,11 +5051,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5179,12 +5179,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/resources/kubecontrollersconfig.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/resources/kubecontrollersconfig.mdx index 6adf0c9311..21cf4e6488 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/resources/kubecontrollersconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/resources/kubecontrollersconfig.mdx @@ -18,7 +18,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -54,7 +54,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-enterprise_versioned_docs/version-3.21-2/release-notes/index.mdx b/calico-enterprise_versioned_docs/version-3.21-2/release-notes/index.mdx index 1e7218ccde..2ea987e83e 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/release-notes/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/release-notes/index.mdx @@ -64,7 +64,7 @@ From the **Web Application Firewall** page, click the **Rulesets** tab to open a * **Log levels for api-server component:** You can now tune the log level for the API server to better support production deployments and troubleshooting scenarios. * **Clusterrolebindings have reduced privileges:** - Clusterrolebindings for the `tigera-operator`, `calico-kube-controller`, and `calico-prometheus-operator` components have been changed to improve $[prodname]'s least-privileged security model. + Clusterrolebindings for the `tigera-operator`, `calico-kube-controller`, and `calico-pickle-operator` components have been changed to improve $[prodname]'s least-privileged security model. * Improved scaling for non-cluster hosts by having them connect to Typha, rather than the Kubernetes apiserver directly. * Added web console support for `AdminNetworkPolicy` and `BaseAdminNetworkPolicy` tiers (view-only). @@ -194,7 +194,7 @@ We've also added more feedback into the UI to keep you informed on the progress * Fixed an issue where CSRs need manual deletion if a non-cluster host's CSR was rejected by the certificate signer. * Fixed an issue where the operator would run into access errors if it was installed in a namespace other than `tigera-operator`. * When IPAM runs out of address space, Calico will try to reclaim empty blocks from other nodes before giving up. -* Avoid writing 0 or negative values to prometheus from linseed, leading to recoverable panics in the logs. +* Avoid writing 0 or negative values to pickle from linseed, leading to recoverable panics in the logs. #### Known issues * There is an issue affecting our Windows images, we are currently investigating it. Please work with your customer success representative for an updated ETA. @@ -269,7 +269,7 @@ May 13, 2026 NAME EXPIRY SIGNER calico-apiserver-certs 2028-05-28T23:56:09Z tigera-operator-signer calico-kube-controllers-metrics-tls 2028-05-28T23:56:09Z tigera-operator-signer - calico-node-prometheus-client-tls 2028-05-29T18:28:09Z tigera-operator-signer + calico-node-pickle-client-tls 2028-05-29T18:28:09Z tigera-operator-signer ... ``` diff --git a/calico-enterprise_versioned_docs/version-3.21-2/releases.json b/calico-enterprise_versioned_docs/version-3.21-2/releases.json index f37b29d43a..99a98a790e 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/releases.json +++ b/calico-enterprise_versioned_docs/version-3.21-2/releases.json @@ -79,10 +79,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.91.0" }, "csi": { @@ -218,17 +218,17 @@ "version": "v3.21.9", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.9", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.9", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.9", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.9", @@ -238,9 +238,9 @@ "version": "v3.21.9", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.9", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.9", @@ -340,10 +340,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.91.0" }, "csi": { @@ -479,17 +479,17 @@ "version": "v3.21.8", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.8", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.8", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.8", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.8", @@ -499,9 +499,9 @@ "version": "v3.21.8", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.8", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.8", @@ -601,10 +601,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.91.0" }, "csi": { @@ -740,17 +740,17 @@ "version": "v3.21.7", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.7", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.7", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.7", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.7", @@ -760,9 +760,9 @@ "version": "v3.21.7", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.7", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.7", @@ -862,10 +862,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -1001,17 +1001,17 @@ "version": "v3.21.6", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.6", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.6", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.6", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.6", @@ -1021,9 +1021,9 @@ "version": "v3.21.6", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.6", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.6", @@ -1123,10 +1123,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -1262,17 +1262,17 @@ "version": "v3.21.5", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.5", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.5", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.5", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.5", @@ -1282,9 +1282,9 @@ "version": "v3.21.5", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.5", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.5", @@ -1384,10 +1384,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -1523,17 +1523,17 @@ "version": "v3.21.4", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.4", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.4", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.4", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.4", @@ -1543,9 +1543,9 @@ "version": "v3.21.4", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.4", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.4", @@ -1645,10 +1645,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -1784,17 +1784,17 @@ "version": "v3.21.3", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.3", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.3", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.3", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.3", @@ -1804,9 +1804,9 @@ "version": "v3.21.3", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.3", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.3", @@ -1906,10 +1906,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.55.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.2" }, "csi": { @@ -2045,17 +2045,17 @@ "version": "v3.21.2", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.2", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.2", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.2", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.2", @@ -2065,9 +2065,9 @@ "version": "v3.21.2", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.2", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.2", @@ -2167,10 +2167,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.54.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.0" }, "csi": { @@ -2306,17 +2306,17 @@ "version": "v3.21.1", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.1", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.1", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.1", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.1", @@ -2326,9 +2326,9 @@ "version": "v3.21.1", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.1", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.1", @@ -2428,10 +2428,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.54.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.0" }, "csi": { @@ -2567,17 +2567,17 @@ "version": "v3.21.0-2.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.0-2.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.0-2.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.0-2.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.0-2.0", @@ -2587,9 +2587,9 @@ "version": "v3.21.0-2.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.0-2.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.0-2.0", @@ -2689,10 +2689,10 @@ "coreos-fluentd": { "version": "1.17.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v2.54.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.76.0" }, "csi": { @@ -2828,17 +2828,17 @@ "version": "v3.21.0-1.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.21.0-1.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.21.0-1.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.21.0-1.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.21.0-1.0", @@ -2848,9 +2848,9 @@ "version": "v3.21.0-1.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.21.0-1.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.21.0-1.0", diff --git a/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx index 0754a384c1..e01b41ea7c 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/FelixConfig/config-params.json b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/FelixConfig/config-params.json index 3c28de306c..e8141cf717 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/FelixConfig/config-params.json +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/FelixConfig/config-params.json @@ -973,7 +973,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1000,7 +1000,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -5572,7 +5572,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5599,7 +5599,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5626,7 +5626,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -5653,7 +5653,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -5680,7 +5680,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js index c220becbf3..f0b20d07d6 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js @@ -149,7 +149,7 @@ EOF`} <> {`helm install calico-enterprise tigera/tigera-operator --version v0.0 \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -157,7 +157,7 @@ EOF`}

    {`helm install calico-enterprise tigera/tigera-operator --version v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} @@ -168,7 +168,7 @@ EOF`} <> {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -176,7 +176,7 @@ EOF`}

    {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js index 5fcb9cdb44..cdd1bcc48b 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js index 825927ad3c..afb6e89b33 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js index d08a015030..82478d4c9d 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js index 9b6180bee7..5d17b47c83 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js index 003e6e431b..67168b5666 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js @@ -8,7 +8,7 @@ import { prodname, baseUrl, filesUrl } from '../../variables'; export default function OpenShiftPrometheusOperator(props) { const createSecret = `oc create secret generic tigera-pull-secret \\ - --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\ + --type=kubernetes.io/dockerconfigjson -n tigera-pickle \\ --from-file=.dockerconfigjson=\n`; const notOSCodeBlock = props.upgradeFrom !== 'OpenSource' ? createSecret : ''; @@ -18,11 +18,11 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryImagePath.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryImagePath.js index 43a125024d..9506ff85cb 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryImagePath.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryImagePath.js @@ -98,11 +98,11 @@ export default function PrivateRegistryImagePath() {

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */} diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryRegular.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryRegular.js index d12ee6e426..cfb71665f2 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryRegular.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/PrivateRegistryRegular.js @@ -94,11 +94,11 @@ export default function PrivateRegistryRegular() { {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js index 97d4f5deda..934b6b6487 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml

  • @@ -80,7 +80,7 @@ export default function UpgradeOperatorSimple(props) {

  • If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now.

    - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml
    • diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx index c8f1627f6c..51d9e5d148 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/helm.mdx index 015d092bda..56f4771f48 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/helm.mdx @@ -96,7 +96,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator --create-namespace ``` @@ -105,7 +105,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator --create-namespace ``` diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 9cfa547111..c8ffd404ac 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx index f52b9dec88..d3981c8913 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx index 86e4afd16a..f0145b5b40 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/manifest-archive.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/manifest-archive.mdx index a252269932..a42ecc985d 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/manifest-archive.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/manifest-archive.mdx @@ -48,7 +48,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index dbd5a2bfa6..e13446b38c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -47,7 +47,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -59,12 +59,12 @@ The following steps assume the Calico deployment is installed on `tigera-operato {'$[version]' === 'master' ? ( `helm upgrade calico tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) : ( `helm upgrade calico tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) } diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index 6c77fdb76c..d15191df3b 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -134,13 +134,13 @@ These steps differ based on your cluster type. If you are unsure of your cluster {'$[version]' === 'master' ? ( `helm upgrade calico-enterprise --values= tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) : ( `helm upgrade calico-enterprise --values= tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) diff --git a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx index c1a6734fe7..c4a8400af8 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx index 486151bd1a..6b1e8d4579 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx @@ -126,12 +126,12 @@ To install a $[prodname] [managed](../standard-install/create-a-managed-cluster# {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx index c20c63a2b9..e071ac1d84 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx @@ -145,11 +145,11 @@ To install a $[prodname] [management](create-a-management-cluster-helm#value) cl {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace`} @@ -233,11 +233,11 @@ For example, if you are using EKS, you must meet the requirements defined in [cr {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.22-2/network-policy/beginners/simple-policy-cnx.mdx b/calico-enterprise_versioned_docs/version-3.22-2/network-policy/beginners/simple-policy-cnx.mdx index c8581977f2..6714c720b7 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/network-policy/beginners/simple-policy-cnx.mdx @@ -92,15 +92,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -118,7 +118,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/comms/secure-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/comms/secure-metrics.mdx index 966b7ce7dd..8da0869472 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/comms/secure-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash - kubectl apply -f calico-prometheus-policy.yaml + kubectl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f typha-prometheus-policy.yaml +kubectl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ kubectl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `kubectl` to apply this policy. ```bash -kubectl apply -f kube-controllers-prometheus-policy.yaml +kubectl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx index 1c52760c9c..606ba91828 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx @@ -56,10 +56,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx index f8ba2c9728..ce40f502e0 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -165,4 +165,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index b15bab97eb..1c2be4cb28 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch @@ -50,11 +50,11 @@ rules. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-storage-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-elasticsearch.rules @@ -132,11 +132,11 @@ have crossed certain thresholds: apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx index d8ce741e6d..464d65a6a9 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx @@ -33,7 +33,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) ### Add license agent in your Kubernetes cluster @@ -62,11 +62,11 @@ In the following example, an alert is configured when the license expiry is fewe apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-license - namespace: tigera-prometheus + name: calico-pickle-license + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-license.rules @@ -89,4 +89,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../prometheus/alertmanager.mdx) +- [Configure Alertmanager](../pickle/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx index 8297fa724a..2a04c6830c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx index c31446657e..1534f898a9 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx index 737ee64166..48e94755c2 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -306,11 +306,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -341,11 +341,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -358,7 +358,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -375,8 +375,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx index 5e9496e09f..f436e2fb9c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -31,11 +31,11 @@ As an example, the range query in this Manifest is 10 seconds. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -56,11 +56,11 @@ To update this alerting rule, to say, execute the query with a range of apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-dp-rate - namespace: tigera-prometheus + name: calico-pickle-dp-rate + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: tigera-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: tigera-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx index 06e2017734..4784b3a6bb 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,7 +14,7 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. #### Prometheus on $[prodnameWindows] @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-prometheus.mdx). +For details, see [Bring your own Prometheus](byo-pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx index 2d6f3f4e96..905ddf7e2d 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoctl/cluster/diags.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoctl/cluster/diags.mdx index 761c43a9bb..ef8b8e3197 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoctl/cluster/diags.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoctl/cluster/diags.mdx @@ -350,11 +350,11 @@ Collecting detailed diags for pod tigera-packetcapture-758ff8c7db-slmd7 in names Collecting diags for pod: tigera-packetcapture-758ff8c7db-slmd7 Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting detailed diags for namespace tigera-pickle... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... ==== Producing a diagnostics bundle. ==== diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoq/host.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoq/host.mdx index dd86ff9088..8755053dab 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoq/host.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/clis/calicoq/host.mdx @@ -35,10 +35,10 @@ Sample output follows. ``` Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 Policies: diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx index a210c88b68..98393bb18e 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx @@ -910,10 +910,10 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -922,7 +922,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -933,7 +933,7 @@ The "config-reloader" container has default resource values set based by the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { "limits": { "cpu": "500m", @@ -975,7 +975,7 @@ The "config-reloader" container has default resource values set based by the Pro ### Alertmanager -To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -987,7 +987,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx index 58c8af5259..cdeb35b55f 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx @@ -855,7 +855,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -950,7 +950,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1121,11 +1121,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2513,7 +2513,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2542,7 +2542,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2601,7 +2601,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3593,8 +3593,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4800,8 +4800,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5372,7 +5372,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5382,7 +5382,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5397,11 +5397,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5526,12 +5526,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/resources/kubecontrollersconfig.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/resources/kubecontrollersconfig.mdx index 21f6da036b..8a584ef740 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/resources/kubecontrollersconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/resources/kubecontrollersconfig.mdx @@ -18,7 +18,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -55,7 +55,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-enterprise_versioned_docs/version-3.22-2/release-notes/index.mdx b/calico-enterprise_versioned_docs/version-3.22-2/release-notes/index.mdx index 9b4471a085..be380dc8a1 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/release-notes/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/release-notes/index.mdx @@ -194,7 +194,7 @@ This Calico Enterprise release is based on [Calico Open Source 3.31](https://doc * Fixed an issue where the operator would run into access errors if it was installed in a namespace other than `tigera-operator`. * Fixed an issue where CSRs need manual deletion if a non-cluster host's CSR was rejected by the certificate signer. * When IPAM runs out of address space, Calico will try to reclaim empty blocks from other nodes before giving up. -* Avoid writing 0 or negative values to prometheus from linseed, leading to recoverable panics in the logs. +* Avoid writing 0 or negative values to pickle from linseed, leading to recoverable panics in the logs. #### Known issues @@ -345,7 +345,7 @@ Use v3.22.4 instead, which includes a fix for this issue. NAME EXPIRY SIGNER calico-apiserver-certs 2028-05-28T23:56:09Z tigera-operator-signer calico-kube-controllers-metrics-tls 2028-05-28T23:56:09Z tigera-operator-signer - calico-node-prometheus-client-tls 2028-05-29T18:28:09Z tigera-operator-signer + calico-node-pickle-client-tls 2028-05-29T18:28:09Z tigera-operator-signer ... ``` diff --git a/calico-enterprise_versioned_docs/version-3.22-2/releases.json b/calico-enterprise_versioned_docs/version-3.22-2/releases.json index 3c52da2b81..ad3561dbe1 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/releases.json +++ b/calico-enterprise_versioned_docs/version-3.22-2/releases.json @@ -59,10 +59,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.11.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.90.1" }, "csi": { @@ -230,17 +230,17 @@ "version": "v3.22.6", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.6", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.6", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.6", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "queryserver": { "version": "v3.22.6", @@ -254,9 +254,9 @@ "version": "v3.22.6", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.6", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.6", @@ -343,10 +343,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.11.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.90.1" }, "csi": { @@ -514,17 +514,17 @@ "version": "v3.22.5", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.5", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.5", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.5", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "queryserver": { "version": "v3.22.5", @@ -538,9 +538,9 @@ "version": "v3.22.5", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.5", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.5", @@ -627,10 +627,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.11.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.90.1" }, "csi": { @@ -798,17 +798,17 @@ "version": "v3.22.4", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.4", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.4", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.4", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "queryserver": { "version": "v3.22.4", @@ -822,9 +822,9 @@ "version": "v3.22.4", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.4", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.4", @@ -934,10 +934,10 @@ "upstream-istio": { "version": "1.28.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.11.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.90.1" }, "csi": { @@ -1069,17 +1069,17 @@ "version": "v3.22.3", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.3", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.3", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.3", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.3", @@ -1089,9 +1089,9 @@ "version": "v3.22.3", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.3", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.3", @@ -1198,10 +1198,10 @@ "upstream-istio": { "version": "1.28.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -1333,17 +1333,17 @@ "version": "v3.22.2", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.2", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.2", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.2", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.2", @@ -1353,9 +1353,9 @@ "version": "v3.22.2", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.2", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.2", @@ -1462,10 +1462,10 @@ "upstream-istio": { "version": "1.28.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -1597,17 +1597,17 @@ "version": "v3.22.1", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.1", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.1", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.1", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.1", @@ -1617,9 +1617,9 @@ "version": "v3.22.1", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.1", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.1", @@ -1723,10 +1723,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -1858,17 +1858,17 @@ "version": "v3.22.0-3.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.0-3.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.0-3.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.0-3.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.0-3.0", @@ -1878,9 +1878,9 @@ "version": "v3.22.0-3.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.0-3.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.0-3.0", @@ -1984,10 +1984,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -2123,17 +2123,17 @@ "version": "v3.22.0-2.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.0-2.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.0-2.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.0-2.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.0-2.0", @@ -2143,9 +2143,9 @@ "version": "v3.22.0-2.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.0-2.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.0-2.0", @@ -2249,10 +2249,10 @@ "coreos-fluentd": { "version": "1.18.0" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.4.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.84.0" }, "csi": { @@ -2388,17 +2388,17 @@ "version": "v3.22.0-1.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.22.0-1.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.22.0-1.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.22.0-1.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni": { "version": "v3.22.0-1.0", @@ -2408,9 +2408,9 @@ "version": "v3.22.0-1.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.22.0-1.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.22.0-1.0", diff --git a/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx index 01b05b33ca..b5d76bb09b 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/FelixConfig/config-params.json b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/FelixConfig/config-params.json index 8f6cd44252..02ae543838 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/FelixConfig/config-params.json +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/FelixConfig/config-params.json @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1216,7 +1216,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1243,7 +1243,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1270,7 +1270,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6036,7 +6036,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6063,7 +6063,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6090,7 +6090,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6117,7 +6117,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6144,7 +6144,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js index c220becbf3..f0b20d07d6 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js @@ -149,7 +149,7 @@ EOF`} <> {`helm install calico-enterprise tigera/tigera-operator --version v0.0 \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -157,7 +157,7 @@ EOF`}

    {`helm install calico-enterprise tigera/tigera-operator --version v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} @@ -168,7 +168,7 @@ EOF`} <> {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -176,7 +176,7 @@ EOF`}

    {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js index e2ce3c2ee3..aa2835c186 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js index 5486fe984f..49e4512999 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js index 694a6c48e1..1c4874586c 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js index 5266d4ca60..8bdb70713c 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js index 003e6e431b..67168b5666 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js @@ -8,7 +8,7 @@ import { prodname, baseUrl, filesUrl } from '../../variables'; export default function OpenShiftPrometheusOperator(props) { const createSecret = `oc create secret generic tigera-pull-secret \\ - --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\ + --type=kubernetes.io/dockerconfigjson -n tigera-pickle \\ --from-file=.dockerconfigjson=\n`; const notOSCodeBlock = props.upgradeFrom !== 'OpenSource' ? createSecret : ''; @@ -18,11 +18,11 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryImagePath.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryImagePath.js index 6a8c9e2882..5a6d7e1ec1 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryImagePath.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryImagePath.js @@ -98,11 +98,11 @@ export default function PrivateRegistryImagePath() {

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */} diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryRegular.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryRegular.js index 872ff86272..a6088dced2 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryRegular.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/PrivateRegistryRegular.js @@ -94,11 +94,11 @@ export default function PrivateRegistryRegular() { {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js index 97d4f5deda..934b6b6487 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml

  • @@ -80,7 +80,7 @@ export default function UpgradeOperatorSimple(props) {

  • If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now.

    - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml
    • diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx index 3d381e1f9a..a11d6219d3 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/helm.mdx index 2e25991691..34fda12800 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/helm.mdx @@ -103,7 +103,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator \ --create-namespace @@ -113,7 +113,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator \ --create-namespace diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 8943823732..f0f640c771 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx index f52b9dec88..d3981c8913 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx index 86e4afd16a..f0145b5b40 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/manifest-archive.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/manifest-archive.mdx index a252269932..a42ecc985d 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/manifest-archive.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/manifest-archive.mdx @@ -48,7 +48,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index dbd5a2bfa6..e13446b38c 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -47,7 +47,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -59,12 +59,12 @@ The following steps assume the Calico deployment is installed on `tigera-operato {'$[version]' === 'master' ? ( `helm upgrade calico tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) : ( `helm upgrade calico tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) } diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index 69516120df..d6c751104b 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -134,13 +134,13 @@ These steps differ based on your cluster type. If you are unsure of your cluster {'$[version]' === 'master' ? ( `helm upgrade calico-enterprise --values= tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) : ( `helm upgrade calico-enterprise --values= tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx index 3f33c16d74..04c12d884c 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx index fa5c7a0587..23054fabf8 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx @@ -133,13 +133,13 @@ To install a $[prodname] [managed](../standard-install/create-a-managed-cluster# {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator \\ diff --git a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx index 4756c0472a..05a17261ec 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx @@ -153,12 +153,12 @@ To install a $[prodname] [management](create-a-management-cluster-helm#value) cl {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace`} @@ -249,12 +249,12 @@ For example, if you are using EKS, you must meet the requirements defined in [cr {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.23-2/network-policy/beginners/simple-policy-cnx.mdx b/calico-enterprise_versioned_docs/version-3.23-2/network-policy/beginners/simple-policy-cnx.mdx index c8581977f2..6714c720b7 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/network-policy/beginners/simple-policy-cnx.mdx @@ -92,15 +92,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -118,7 +118,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx index 88ff7dd86b..c3579b10e8 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx index 1bedcc63bd..2081bb65c8 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/observability/review-unused-network-policies.mdx b/calico-enterprise_versioned_docs/version-3.23-2/observability/review-unused-network-policies.mdx index 69c22e2483..4126608ad8 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/observability/review-unused-network-policies.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/observability/review-unused-network-policies.mdx @@ -71,7 +71,7 @@ WARNING: Some unused policies have been recently edited! Unused Policies since 2026-01-14T00:00:00Z (7) KIND NAMESPACE NAME PREV GENS EVALUATED RECENTLY EDITED NetworkPolicy calico-system calico-system.default-deny Yes No -NetworkPolicy tigera-prometheus calico-system.default-deny No No +NetworkPolicy tigera-pickle calico-system.default-deny No No GlobalNetworkPolicy N/A anp-v2 No No KubernetesNetworkPolicy test-policies k8snp-v2 Yes Yes StagedKubernetesNetworkPolicy test-policies sknp-v2 Yes No @@ -121,7 +121,7 @@ $ calicoctl review unused-policies -o json { "kind": "NetworkPolicy", "name": "calico-system.default-deny", - "namespace": "tigera-prometheus", + "namespace": "tigera-pickle", "generation": 1, "creationTimestamp": "2026-04-21T16:26:00Z", "lastUpdate": "2026-04-21T16:26:00Z", diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/comms/index.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/comms/index.mdx index b21a097c9f..58c1790710 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/comms/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/comms/index.mdx @@ -49,9 +49,9 @@ The **Deployed to** column shows the namespace where the operator places the sec |---|---|---|---| | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `internal-manager-tls` | `calico-manager` | `calico-system` | Manager/tigera-secure | | `intrusion-detection-tls` | `intrusion-detection-tls` | `tigera-intrusion-detection` | IntrusionDetection/tigera-secure | @@ -60,8 +60,8 @@ The **Deployed to** column shows the namespace where the operator places the sec | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `policy-recommendation-tls` | `policy-recommendation-tls` | `calico-system` | PolicyRecommendation/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | -| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-prometheus` | Monitor/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-pickle` | Monitor/tigera-secure | | `tigera-secure-elasticsearch-cert` | `tigera-secure-es-gateway-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-internal-elasticsearch-cert` | `tigera-secure-es-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-kibana-cert` | `tigera-secure-kb-http` | `tigera-kibana` | LogStorage/tigera-secure | diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx index 87d695c066..a9e1b147e7 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx @@ -44,10 +44,10 @@ See [Provide TLS certificates for $[prodname] components](./comms/index.mdx) for ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx index fe4ff36e86..0b65755575 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx @@ -61,10 +61,10 @@ The Tigera Operator reports license condition in `tigerastatus`, including a war $[prodname] provides license metrics, such as the number of days until license expiration, through the **License Agent** component and Prometheus. For details on deploying the license agent and creating expiration alerts, see [License metrics](monitor/metrics/license-agent.mdx). -To route license alerts, see [Configure Alertmanager](monitor/prometheus/alertmanager.mdx). +To route license alerts, see [Configure Alertmanager](monitor/pickle/alertmanager.mdx). ## Additional resources - [LicenseKey resource](../reference/resources/licensekey.mdx) -- [Configure Alertmanager](monitor/prometheus/alertmanager.mdx) -- [Configure Prometheus](monitor/prometheus/configure-prometheus.mdx) +- [Configure Alertmanager](monitor/pickle/alertmanager.mdx) +- [Configure Prometheus](monitor/pickle/configure-pickle.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx index c33bad7fb1..61bf089dc9 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -164,4 +164,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index b15bab97eb..1c2be4cb28 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch @@ -50,11 +50,11 @@ rules. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-storage-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-elasticsearch.rules @@ -132,11 +132,11 @@ have crossed certain thresholds: apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx index 4acbf50c18..f1386fbcef 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx @@ -27,7 +27,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) ### Add license agent in your Kubernetes cluster @@ -56,11 +56,11 @@ In the following example, an alert is configured when the license expiry is fewe apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-license - namespace: tigera-prometheus + name: calico-pickle-license + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-license.rules @@ -83,4 +83,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../prometheus/alertmanager.mdx) +- [Configure Alertmanager](../pickle/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx index 8297fa724a..2a04c6830c 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx index c31446657e..1534f898a9 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx index 737ee64166..48e94755c2 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -26,13 +26,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -41,7 +41,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -52,10 +52,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -67,14 +67,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -90,18 +90,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -113,11 +113,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -131,18 +131,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -154,11 +154,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -172,18 +172,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -195,11 +195,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -213,18 +213,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -236,11 +236,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -257,7 +257,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -306,11 +306,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -341,11 +341,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -358,7 +358,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -375,8 +375,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx index ce12058105..ba84d577af 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -32,10 +32,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -57,10 +57,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: calico-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: calico-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx index 06e2017734..4784b3a6bb 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,7 +14,7 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. #### Prometheus on $[prodnameWindows] @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-prometheus.mdx). +For details, see [Bring your own Prometheus](byo-pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx index 760400063c..064db5744d 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoctl/cluster/diags.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoctl/cluster/diags.mdx index af93e03ba4..43dc2c8364 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoctl/cluster/diags.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoctl/cluster/diags.mdx @@ -349,11 +349,11 @@ Collecting detailed diags for pod tigera-packetcapture-758ff8c7db-slmd7 in names Collecting diags for pod: tigera-packetcapture-758ff8c7db-slmd7 Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting detailed diags for namespace tigera-pickle... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... ==== Producing a diagnostics bundle. ==== diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoq/host.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoq/host.mdx index dd86ff9088..8755053dab 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoq/host.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/clis/calicoq/host.mdx @@ -35,10 +35,10 @@ Sample output follows. ``` Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 Policies: diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx index 7281339d8f..5ffd6cfa40 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx @@ -910,10 +910,10 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -922,7 +922,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -933,7 +933,7 @@ The "config-reloader" container has default resource values set based by the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { "limits": { "cpu": "500m", @@ -975,7 +975,7 @@ The "config-reloader" container has default resource values set based by the Pro ### Alertmanager -To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -987,7 +987,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx index bd9849c941..dad7a2f144 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx index 0e80336f64..3ede2822ef 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx @@ -855,7 +855,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -950,7 +950,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1121,11 +1121,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2514,7 +2514,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2543,7 +2543,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2602,7 +2602,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3594,8 +3594,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4801,8 +4801,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5373,7 +5373,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5383,7 +5383,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5398,11 +5398,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5527,12 +5527,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/resources/kubecontrollersconfig.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/resources/kubecontrollersconfig.mdx index 9c51a167e2..e95c1d4d26 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/resources/kubecontrollersconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/resources/kubecontrollersconfig.mdx @@ -24,7 +24,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -61,7 +61,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-enterprise_versioned_docs/version-3.23-2/releases.json b/calico-enterprise_versioned_docs/version-3.23-2/releases.json index 67315c1596..effbd026d0 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/releases.json +++ b/calico-enterprise_versioned_docs/version-3.23-2/releases.json @@ -59,10 +59,10 @@ "coreos-fluentd": { "version": "1.19.3" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.12.0" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.91.0" }, "csi": { @@ -230,17 +230,17 @@ "version": "v3.23.1", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.23.1", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.23.1", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.23.1", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "queryserver": { "version": "v3.23.1", @@ -258,9 +258,9 @@ "version": "v3.23.1", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.23.1", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.23.1", @@ -351,10 +351,10 @@ "coreos-fluentd": { "version": "1.19.2" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.11.3" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.90.1" }, "csi": { @@ -522,17 +522,17 @@ "version": "v3.23.0-2.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.23.0-2.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.23.0-2.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.23.0-2.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "queryserver": { "version": "v3.23.0-2.0", @@ -550,9 +550,9 @@ "version": "v3.23.0-2.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.23.0-2.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.23.0-2.0", @@ -643,10 +643,10 @@ "coreos-fluentd": { "version": "1.19.1" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.9.1" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.88.0" }, "csi": { @@ -814,17 +814,17 @@ "version": "v3.23.0-1.0", "image": "tigera/policy-recommendation" }, - "prometheus": { + "pickle": { "version": "v3.23.0-1.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.23.0-1.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.23.0-1.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "queryserver": { "version": "v3.23.0-1.0", @@ -842,9 +842,9 @@ "version": "v3.23.0-1.0", "image": "tigera/cni-windows" }, - "tigera-prometheus-service": { + "tigera-pickle-service": { "version": "v3.23.0-1.0", - "image": "tigera/prometheus-service" + "image": "tigera/pickle-service" }, "typha": { "version": "v3.23.0-1.0", diff --git a/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx index 01b05b33ca..b5d76bb09b 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/FelixConfig/config-params.json b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/FelixConfig/config-params.json index 8f6cd44252..02ae543838 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/FelixConfig/config-params.json +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/FelixConfig/config-params.json @@ -1027,7 +1027,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1054,7 +1054,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1081,7 +1081,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1108,7 +1108,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1135,7 +1135,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1162,7 +1162,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1189,7 +1189,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -1216,7 +1216,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1243,7 +1243,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1270,7 +1270,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6036,7 +6036,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCAFile", "NameEnvVar": "FELIX_PrometheusReporterCAFile", - "NameYAML": "prometheusReporterCAFile", + "NameYAML": "pickleReporterCAFile", "NameGoAPI": "PrometheusReporterCAFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6063,7 +6063,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterCertFile", "NameEnvVar": "FELIX_PrometheusReporterCertFile", - "NameYAML": "prometheusReporterCertFile", + "NameYAML": "pickleReporterCertFile", "NameGoAPI": "PrometheusReporterCertFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6090,7 +6090,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterEnabled", "NameEnvVar": "FELIX_PrometheusReporterEnabled", - "NameYAML": "prometheusReporterEnabled", + "NameYAML": "pickleReporterEnabled", "NameGoAPI": "PrometheusReporterEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -6117,7 +6117,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterKeyFile", "NameEnvVar": "FELIX_PrometheusReporterKeyFile", - "NameYAML": "prometheusReporterKeyFile", + "NameYAML": "pickleReporterKeyFile", "NameGoAPI": "PrometheusReporterKeyFile", "StringSchema": "Path to file, which must exist", "StringSchemaHTML": "Path to file, which must exist", @@ -6144,7 +6144,7 @@ "GroupWithSortPrefix": "40 Flow logs: Prometheus reports", "NameConfigFile": "PrometheusReporterPort", "NameEnvVar": "FELIX_PrometheusReporterPort", - "NameYAML": "prometheusReporterPort", + "NameYAML": "pickleReporterPort", "NameGoAPI": "PrometheusReporterPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js index c220becbf3..f0b20d07d6 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/GettingStartedInstallOnClustersKubernetesHelm.js @@ -149,7 +149,7 @@ EOF`} <> {`helm install calico-enterprise tigera/tigera-operator --version v0.0 \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -157,7 +157,7 @@ EOF`}

    {`helm install calico-enterprise tigera/tigera-operator --version v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} @@ -168,7 +168,7 @@ EOF`} <> {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`}

    @@ -176,7 +176,7 @@ EOF`}

    {`helm install calico-enterprise tigera-operator-${chart_version_name}.tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator`} diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js index 0a909b39e6..f99e2da1c4 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js index c971567072..6ee617a2f1 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js index 11bfe1310b..5539e101b4 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js index 62e7c87125..977f588d77 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js index 003e6e431b..67168b5666 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js @@ -8,7 +8,7 @@ import { prodname, baseUrl, filesUrl } from '../../variables'; export default function OpenShiftPrometheusOperator(props) { const createSecret = `oc create secret generic tigera-pull-secret \\ - --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\ + --type=kubernetes.io/dockerconfigjson -n tigera-pickle \\ --from-file=.dockerconfigjson=\n`; const notOSCodeBlock = props.upgradeFrom !== 'OpenSource' ? createSecret : ''; @@ -18,11 +18,11 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryImagePath.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryImagePath.js index 6a8c9e2882..5a6d7e1ec1 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryImagePath.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryImagePath.js @@ -98,11 +98,11 @@ export default function PrivateRegistryImagePath() {

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */} diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryRegular.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryRegular.js index 872ff86272..a6088dced2 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryRegular.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/PrivateRegistryRegular.js @@ -94,11 +94,11 @@ export default function PrivateRegistryRegular() { {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    If you are installing Prometheus operator as part of {prodname}, then before applying{' '} - tigera-prometheus-operator.yaml, modify registry references to use your custom registry: + tigera-pickle-operator.yaml, modify registry references to use your custom registry:

    - {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml`} + {`sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a \ imagePullSecrets:\\n\ - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml`} {/* The second 'sed' should be removed once operator launches Prometheus & Alertmanager */}

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js index 97d4f5deda..934b6b6487 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml

  • @@ -80,7 +80,7 @@ export default function UpgradeOperatorSimple(props) {

  • If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now.

    - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml
    • diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx index 5f2f05f16b..73db0eeb15 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/helm.mdx index dae22733ce..5c541c3808 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/helm.mdx @@ -103,7 +103,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator \ --create-namespace @@ -113,7 +113,7 @@ To install a standard $[prodname] cluster with Helm: ```bash helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ --namespace tigera-operator \ --create-namespace diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx index fcd5931fc4..10c59cd86d 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx index 9209e9ad2a..53c8fb1477 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx index 1555d904a6..f53e85ef00 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/manifest-archive.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/manifest-archive.mdx index a252269932..a42ecc985d 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/manifest-archive.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/manifest-archive.mdx @@ -48,7 +48,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 51dcbb131c..6ee8ea4480 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -60,7 +60,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -69,7 +69,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -84,12 +84,12 @@ The following steps assume the Calico deployment is installed on `tigera-operato {'$[version]' === 'master' ? ( `helm upgrade calico tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) : ( `helm upgrade calico tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --namespace tigera-operator` ) } diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index 4380f070bb..69b63788b1 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -86,7 +86,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -95,7 +95,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -156,13 +156,13 @@ These steps differ based on your cluster type. If you are unsure of your cluster {'$[version]' === 'master' ? ( `helm upgrade calico-enterprise --values= tigera-operator-v0.0.tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) : ( `helm upgrade calico-enterprise --values= tigera-operator-$[chart_version_name].tgz \\ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator` ) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx index 3f33c16d74..04c12d884c 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx index fa5c7a0587..23054fabf8 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx @@ -133,13 +133,13 @@ To install a $[prodname] [managed](../standard-install/create-a-managed-cluster# {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --set logStorage.enabled=false --set manager.enabled=false \\ --namespace tigera-operator \\ diff --git a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx index 4756c0472a..05a17261ec 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx @@ -153,12 +153,12 @@ To install a $[prodname] [management](create-a-management-cluster-helm#value) cl {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace`} @@ -249,12 +249,12 @@ For example, if you are using EKS, you must meet the requirements defined in [cr {'$[version]' === 'master' ? `helm install $[prodnamedash] tigera/tigera-operator --version tigera-operator-v0.0 -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace` : `helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz -f values.yaml \\ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \\ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \\ --set-file licenseKeyContent= \\ --namespace tigera-operator \\ --create-namespace`} diff --git a/calico-enterprise_versioned_docs/version-3.24-1/network-policy/beginners/simple-policy-cnx.mdx b/calico-enterprise_versioned_docs/version-3.24-1/network-policy/beginners/simple-policy-cnx.mdx index c8581977f2..6714c720b7 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/network-policy/beginners/simple-policy-cnx.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/network-policy/beginners/simple-policy-cnx.mdx @@ -92,15 +92,15 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ``` Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -118,7 +118,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace rules that deny or allow that endpoint as a packet source or destination. Focusing on the - `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to diff --git a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx index 88ff7dd86b..c3579b10e8 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx index 1bedcc63bd..2081bb65c8 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/observability/review-unused-network-policies.mdx b/calico-enterprise_versioned_docs/version-3.24-1/observability/review-unused-network-policies.mdx index 69c22e2483..4126608ad8 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/observability/review-unused-network-policies.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/observability/review-unused-network-policies.mdx @@ -71,7 +71,7 @@ WARNING: Some unused policies have been recently edited! Unused Policies since 2026-01-14T00:00:00Z (7) KIND NAMESPACE NAME PREV GENS EVALUATED RECENTLY EDITED NetworkPolicy calico-system calico-system.default-deny Yes No -NetworkPolicy tigera-prometheus calico-system.default-deny No No +NetworkPolicy tigera-pickle calico-system.default-deny No No GlobalNetworkPolicy N/A anp-v2 No No KubernetesNetworkPolicy test-policies k8snp-v2 Yes Yes StagedKubernetesNetworkPolicy test-policies sknp-v2 Yes No @@ -121,7 +121,7 @@ $ calicoctl review unused-policies -o json { "kind": "NetworkPolicy", "name": "calico-system.default-deny", - "namespace": "tigera-prometheus", + "namespace": "tigera-pickle", "generation": 1, "creationTimestamp": "2026-04-21T16:26:00Z", "lastUpdate": "2026-04-21T16:26:00Z", diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/comms/index.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/comms/index.mdx index c7275dbc71..4d69b1f28c 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/comms/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/comms/index.mdx @@ -50,9 +50,9 @@ The **Deployed to** column shows the namespace where the operator places the sec |---|---|---|---| | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `internal-manager-tls` | `calico-manager` | `calico-system` | Manager/tigera-secure | | `intrusion-detection-tls` | `intrusion-detection-tls` | `tigera-intrusion-detection` | IntrusionDetection/tigera-secure | @@ -61,8 +61,8 @@ The **Deployed to** column shows the namespace where the operator places the sec | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `policy-recommendation-tls` | `policy-recommendation-tls` | `calico-system` | PolicyRecommendation/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | -| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-prometheus` | Monitor/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-pickle` | Monitor/tigera-secure | | `tigera-secure-elasticsearch-cert` | `tigera-secure-es-gateway-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-internal-elasticsearch-cert` | `tigera-secure-es-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-kibana-cert` | `tigera-secure-kb-http` | `tigera-kibana` | LogStorage/tigera-secure | diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx index 50185d43f2..222f8dbce8 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx @@ -46,10 +46,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx index 30579f20d1..8a5cd015c0 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx @@ -73,7 +73,7 @@ These metrics are scraped by the built-in Prometheus instance via the `tigera-op $[prodname] installs PrometheusRule resources with alerting rules for license expiration. You can view them with: ```bash -kubectl -n tigera-prometheus get prometheusrule calico -o yaml +kubectl -n tigera-pickle get picklerule calico -o yaml ``` The built-in rules include: @@ -81,10 +81,10 @@ The built-in rules include: - **LicenseExpiringWarning**: fires when the license expires in less than 30 days - **LicenseExpiringCritical**: fires when the license expires in less than 7 days, or is invalid -To route these alerts, see [Configure Alertmanager](monitor/prometheus/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](monitor/pickle/alertmanager.mdx). ## Additional resources - [LicenseKey resource](../reference/resources/licensekey.mdx) -- [Configure Alertmanager](monitor/prometheus/alertmanager.mdx) -- [Configure Prometheus](monitor/prometheus/configure-prometheus.mdx) +- [Configure Alertmanager](monitor/pickle/alertmanager.mdx) +- [Configure Prometheus](monitor/pickle/configure-pickle.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx index c33bad7fb1..61bf089dc9 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx @@ -77,9 +77,9 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 1. Verify you can access the metrics. @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -164,4 +164,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources -- [Configuring Prometheus](../prometheus/index.mdx) +- [Configuring Prometheus](../pickle/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index b15bab97eb..1c2be4cb28 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch @@ -50,11 +50,11 @@ rules. apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-storage-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-elasticsearch.rules @@ -132,11 +132,11 @@ have crossed certain thresholds: apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring - namespace: tigera-prometheus + name: tigera-pickle-log-collection-monitoring + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: tigera-log-collection.rules diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx index 645a2952b7..dc471492dc 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx @@ -107,7 +107,7 @@ The `tigera_operator_tls_certificate_expiry_timestamp_seconds` metric reports th $[prodname] installs a PrometheusRule resource named `calico` with alerting rules that use these metrics. You can view it with: ```bash -kubectl -n tigera-prometheus get prometheusrule calico -o yaml +kubectl -n tigera-pickle get picklerule calico -o yaml ``` The built-in rules include: @@ -124,10 +124,10 @@ The built-in rules include: | `ComponentProgressingWarning` | Component progressing for > 15m | warning | | `ComponentProgressingCritical` | Component progressing for > 30m | critical | -To route these alerts, see [Configure Alertmanager](../prometheus/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](../pickle/alertmanager.mdx). ## Additional resources - [License expiration and renewal](../../license-options.mdx) -- [Configure Prometheus](../prometheus/configure-prometheus.mdx) -- [BYO Prometheus](../prometheus/byo-prometheus.mdx) +- [Configure Prometheus](../pickle/configure-pickle.mdx) +- [BYO Prometheus](../pickle/byo-pickle.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx index 8297fa724a..2a04c6830c 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../prometheus/index.mdx) +[Configuring Prometheus configuration](../pickle/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx index c31446657e..1534f898a9 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -43,11 +43,11 @@ More detailed information about Alertmanager is available in the [upstream docum ``` Your changes should be applied in a few seconds by the config-reloader -container inside the alertmanager pod launched by the prometheus-operator +container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) +[route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx index 8e46b69f5a..f9db9884e8 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx @@ -27,13 +27,13 @@ $[prodname] uses the Prometheus monitoring tool to scrape metrics from instrumen **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](../../../release-notes/index.mdx) (`coreos-pickle`). ## How to - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -42,7 +42,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -53,10 +53,10 @@ The following example shows a Prometheus server installed in namespace "external name: tigera-secure spec: externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](../../../reference/installation/api.mdx). @@ -68,14 +68,14 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus - kubectl get servicemonitor -n $NS tigera-external-prometheus - kubectl get serviceaccount -n $NS tigera-external-prometheus - kubectl get secret -n $NS tigera-external-prometheus - kubectl get clusterrole tigera-external-prometheus - kubectl get clusterrolebinding tigera-external-prometheus + export NS=external-pickle + kubectl get servicemonitor -n $NS tigera-external-pickle + kubectl get serviceaccount -n $NS tigera-external-pickle + kubectl get secret -n $NS tigera-external-pickle + kubectl get clusterrole tigera-external-pickle + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly @@ -91,18 +91,18 @@ components directly using mTLS, or if you wish to enable metrics that are disabl 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -114,11 +114,11 @@ components directly using mTLS, or if you wish to enable metrics that are disabl Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -132,18 +132,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -155,11 +155,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -173,18 +173,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -196,11 +196,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -214,18 +214,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -237,11 +237,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -258,7 +258,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -269,7 +269,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). **For Windows nodes, create a service to expose Felix metrics** @@ -307,11 +307,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -342,11 +342,11 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -360,18 +360,18 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -383,11 +383,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/prometheus/operator-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/pickle/operator-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -400,7 +400,7 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 1. Browse to the Prometheus dashboard: http://localhost:9090. @@ -417,8 +417,8 @@ section. 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx index ce12058105..ba84d577af 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,18 +12,18 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -32,10 +32,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -57,10 +57,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -77,15 +77,15 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) -and [Queries](https://prometheus.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) +and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest -in the `tigera-prometheus` namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The +in the `tigera-pickle` namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. @@ -96,11 +96,11 @@ more than 5 minutes, save the following to a file, say `calico-node-down-alert.y apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down - namespace: tigera-prometheus + name: calico-pickle-calico-node-down + namespace: tigera-pickle labels: - role: tigera-prometheus-rules - prometheus: calico-node-prometheus + role: tigera-pickle-rules + pickle: calico-node-pickle spec: groups: - name: calico.rules @@ -121,15 +121,15 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ### New alerting rule for monitoring BGP peers Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP -peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels -`role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels +peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels +`role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” @@ -141,10 +141,10 @@ apiVersion: monitoring.coreos.com/v1 kind: PrometheusRule metadata: labels: - prometheus: calico-node-prometheus - role: tigera-prometheus-rules - name: calico-prometheus-peer-status-not-established - namespace: tigera-prometheus + pickle: calico-node-pickle + role: tigera-pickle-rules + name: calico-pickle-peer-status-not-established + namespace: tigera-pickle spec: groups: - name: calico.rules @@ -166,9 +166,9 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). ## Additional Alerting Rules @@ -261,7 +261,7 @@ the ServiceMonitor manifest. To change the interval: - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and @@ -271,9 +271,9 @@ the ServiceMonitor manifest. To change the interval: kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader -container inside the prometheus pod launched by the prometheus-operator -(usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader +container inside the pickle pod launched by the pickle-operator +(usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -283,7 +283,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -306,7 +306,7 @@ apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: team: network-operators spec: @@ -325,16 +325,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx index 06e2017734..4784b3a6bb 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options @@ -14,7 +14,7 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. #### Prometheus on $[prodnameWindows] @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-prometheus.mdx). +For details, see [Bring your own Prometheus](byo-pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx index 3da4e4cd8b..42fa1566d9 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx @@ -29,13 +29,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components @@ -109,7 +109,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoctl/cluster/diags.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoctl/cluster/diags.mdx index af93e03ba4..43dc2c8364 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoctl/cluster/diags.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoctl/cluster/diags.mdx @@ -349,11 +349,11 @@ Collecting detailed diags for pod tigera-packetcapture-758ff8c7db-slmd7 in names Collecting diags for pod: tigera-packetcapture-758ff8c7db-slmd7 Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting detailed diags for namespace tigera-pickle... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... ==== Producing a diagnostics bundle. ==== diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoq/host.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoq/host.mdx index dd86ff9088..8755053dab 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoq/host.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/clis/calicoq/host.mdx @@ -35,10 +35,10 @@ Sample output follows. ``` Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 Policies: diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx index 606294ae87..afaedd8ab0 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx @@ -910,10 +910,10 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -922,7 +922,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -933,7 +933,7 @@ The "config-reloader" container has default resource values set based by the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { "limits": { "cpu": "500m", @@ -975,7 +975,7 @@ The "config-reloader" container has default resource values set based by the Pro ### Alertmanager -To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](../../reference/installation/api.mdx#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -987,7 +987,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx index bd9849c941..dad7a2f144 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx index cd280156b9..803fe9b05d 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx @@ -882,7 +882,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, cni-plugins, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, cni-plugins, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -979,7 +979,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1267,11 +1267,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -2204,7 +2204,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | ### EnvoySettings @@ -2233,7 +2233,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` _[ServiceMonitor](#servicemonitor)_ | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` _string_ | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | @@ -2294,7 +2294,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the Fluentd DaemonSet init container by name.
    Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | @@ -3316,8 +3316,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -4563,8 +4563,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[Alertmanager](#alertmanager)_ | (Optional) Alertmanager is the configuration for the Alertmanager. | @@ -5217,7 +5217,7 @@ _Appears in:_ - [ManagerDeploymentContainer](#managerdeploymentcontainer) - [PacketCaptureAPIDeploymentContainer](#packetcaptureapideploymentcontainer) - [PolicyRecommendationDeploymentContainer](#policyrecommendationdeploymentcontainer) -- [PrometheusContainer](#prometheuscontainer) +- [PrometheusContainer](#picklecontainer) - [TyphaDeploymentContainer](#typhadeploymentcontainer) - [WhiskerDeploymentContainer](#whiskerdeploymentcontainer) @@ -5255,7 +5255,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5265,7 +5265,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --- | --- | @@ -5282,11 +5282,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5411,12 +5411,12 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | --- | --- | -| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-prometheus | -| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` _object (keys:string, values:string)_ | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up.
    Default: k8s-app=tigera-pickle | +| `endpoints` _[Endpoint](#endpoint) array_ | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/resources/kubecontrollersconfig.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/resources/kubecontrollersconfig.mdx index 6f103a7381..7b0d550bcc 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/resources/kubecontrollersconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/resources/kubecontrollersconfig.mdx @@ -24,7 +24,7 @@ metadata: spec: logSeverityScreen: Info healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -63,7 +63,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers diff --git a/calico-enterprise_versioned_docs/version-3.24-1/releases.json b/calico-enterprise_versioned_docs/version-3.24-1/releases.json index 2319b0d3ae..45a4618671 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/releases.json +++ b/calico-enterprise_versioned_docs/version-3.24-1/releases.json @@ -39,10 +39,10 @@ "coreos-fluentd": { "version": "1.19.3" }, - "coreos-prometheus": { + "coreos-pickle": { "version": "v3.12.0" }, - "coreos-prometheus-operator": { + "coreos-pickle-operator": { "version": "v0.91.0" }, "deep-packet-inspection": { @@ -150,17 +150,17 @@ "version": "v3.24.0-1.0", "image": "tigera/node-windows" }, - "prometheus": { + "pickle": { "version": "v3.24.0-1.0", - "image": "tigera/prometheus" + "image": "tigera/pickle" }, - "prometheus-config-reloader": { + "pickle-config-reloader": { "version": "v3.24.0-1.0", - "image": "tigera/prometheus-config-reloader" + "image": "tigera/pickle-config-reloader" }, - "prometheus-operator": { + "pickle-operator": { "version": "v3.24.0-1.0", - "image": "tigera/prometheus-operator" + "image": "tigera/pickle-operator" }, "tigera-cni-windows": { "version": "v3.24.0-1.0", diff --git a/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx index 01b05b33ca..b5d76bb09b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json index a59ed81a8c..dc26064297 100644 --- a/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json @@ -704,13 +704,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/support", + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -1004,7 +1004,7 @@ }, "items": [ "reference/component-resources/kube-controllers/configuration", - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -1025,7 +1025,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] @@ -1040,7 +1040,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/prometheus" + "reference/component-resources/typha/pickle" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json index bb91910248..c30c2ccdcd 100644 --- a/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json @@ -711,13 +711,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/support", + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -1011,7 +1011,7 @@ }, "items": [ "reference/component-resources/kube-controllers/configuration", - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -1032,7 +1032,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] @@ -1047,7 +1047,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/prometheus" + "reference/component-resources/typha/pickle" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json index 799117c106..650a979e79 100644 --- a/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json @@ -733,13 +733,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/support", + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -1035,7 +1035,7 @@ }, "items": [ "reference/component-resources/kube-controllers/configuration", - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -1056,7 +1056,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] @@ -1071,7 +1071,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/prometheus" + "reference/component-resources/typha/pickle" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json index 7699ec4f01..07f56c9ebe 100644 --- a/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json @@ -733,13 +733,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/support", + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -1048,7 +1048,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -1069,7 +1069,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] @@ -1084,7 +1084,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/prometheus" + "reference/component-resources/typha/pickle" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json index 5ac9289392..8cf6025d44 100644 --- a/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json @@ -772,13 +772,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/prometheus/index" + "id": "operations/monitor/pickle/index" }, "items": [ - "operations/monitor/prometheus/support", - "operations/monitor/prometheus/byo-prometheus", - "operations/monitor/prometheus/configure-prometheus", - "operations/monitor/prometheus/alertmanager" + "operations/monitor/pickle/support", + "operations/monitor/pickle/byo-pickle", + "operations/monitor/pickle/configure-pickle", + "operations/monitor/pickle/alertmanager" ] }, { @@ -1071,7 +1071,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/prometheus" + "reference/component-resources/kube-controllers/pickle" ] }, { @@ -1092,7 +1092,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/prometheus" + "reference/component-resources/node/felix/pickle" ] } ] @@ -1107,7 +1107,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/prometheus" + "reference/component-resources/typha/pickle" ] } ] diff --git a/calico/_includes/components/FelixConfig/config-params.json b/calico/_includes/components/FelixConfig/config-params.json index ac9d6ca255..13736d91f6 100644 --- a/calico/_includes/components/FelixConfig/config-params.json +++ b/calico/_includes/components/FelixConfig/config-params.json @@ -965,7 +965,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -991,7 +991,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "String", "StringSchemaHTML": "String", @@ -1017,7 +1017,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "String", "StringSchemaHTML": "String", @@ -1043,7 +1043,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1069,7 +1069,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1095,7 +1095,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1121,7 +1121,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "String", "StringSchemaHTML": "String", @@ -1147,7 +1147,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1173,7 +1173,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1199,7 +1199,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", diff --git a/calico/network-policy/comms/secure-metrics.mdx b/calico/network-policy/comms/secure-metrics.mdx index f0284404fd..65657525db 100644 --- a/calico/network-policy/comms/secure-metrics.mdx +++ b/calico/network-policy/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico/networking/configuring/add-maglev-load-balancing.mdx b/calico/networking/configuring/add-maglev-load-balancing.mdx index b6ac582c63..ca3c562212 100644 --- a/calico/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico/operations/monitor/monitor-component-metrics.mdx b/calico/operations/monitor/monitor-component-metrics.mdx index 3b9f410ce7..60e93e1edd 100644 --- a/calico/operations/monitor/monitor-component-metrics.mdx +++ b/calico/operations/monitor/monitor-component-metrics.mdx @@ -67,7 +67,7 @@ This tutorial will go through the necessary steps to implement basic monitoring #### **Felix configuration** -Felix prometheus metrics are **disabled** by default. +Felix pickle metrics are **disabled** by default. :::note A comprehensive list of configuration values can be [found at this link](../../reference/felix/configuration.mdx). @@ -80,7 +80,7 @@ Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -93,7 +93,7 @@ felixconfiguration.projectcalico.org/default patched ```bash -calicoctl patch felixconfiguration default --patch '{"spec":{"prometheusMetricsEnabled": true}}' +calicoctl patch felixconfiguration default --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -348,14 +348,14 @@ Setting this value to zero will disable metrics in the kube-controllers pod. ```bash -kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"prometheusMetricsPort": 9095}}' +kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` ```bash -calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"prometheusMetricsPort": 9095}}' +calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` @@ -399,7 +399,7 @@ kubectl apply -f - < ```bash -kubectl patch felixConfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": false}}' +kubectl patch felixConfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": false}}' kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/spec/typhaMetricsPort"}]' ``` @@ -690,7 +690,7 @@ kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/sp ```bash -calicoctl patch felixConfiguration default --patch '{"spec":{"prometheusMetricsEnabled": false}}' +calicoctl patch felixConfiguration default --patch '{"spec":{"pickleMetricsEnabled": false}}' ``` @@ -700,8 +700,8 @@ Finally, remove the namespace and RBAC permissions. ```bash kubectl delete namespace calico-monitoring -kubectl delete ClusterRole calico-prometheus-user -kubectl delete clusterrolebinding calico-prometheus-user +kubectl delete ClusterRole calico-pickle-user +kubectl delete clusterrolebinding calico-pickle-user ``` ## Best practices diff --git a/calico/operations/monitor/monitor-component-visual.mdx b/calico/operations/monitor/monitor-component-visual.mdx index 8af07a94da..509cbd71f8 100644 --- a/calico/operations/monitor/monitor-component-visual.mdx +++ b/calico/operations/monitor/monitor-component-visual.mdx @@ -37,18 +37,18 @@ This tutorial will go through the necessary steps to create $[prodname] metrics ### Preparing Prometheus -Here you will create a service to make your prometheus visible to Grafana. +Here you will create a service to make your pickle visible to Grafana. ```bash kubectl apply -f - < - +     ## Typha - + diff --git a/calico/reference/installation/_api.mdx b/calico/reference/installation/_api.mdx index 32ae05941a..21702680f6 100644 --- a/calico/reference/installation/_api.mdx +++ b/calico/reference/installation/_api.mdx @@ -607,7 +607,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -704,7 +704,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1864,8 +1864,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | diff --git a/calico/reference/resources/kubecontrollersconfig.mdx b/calico/reference/resources/kubecontrollersconfig.mdx index e2d6f3f563..738baa47f2 100644 --- a/calico/reference/resources/kubecontrollersconfig.mdx +++ b/calico/reference/resources/kubecontrollersconfig.mdx @@ -19,7 +19,7 @@ spec: logSeverityScreen: Info healthChecks: Enabled etcdV3CompactionPeriod: 10m - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -66,7 +66,7 @@ spec: | ---------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------- | --------------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | etcdV3CompactionPeriod | The period between etcdv3 compaction requests. Only applies when using etcd as the $[prodname] datastore. | Set to 0 to disable, > 0 to enable | [Duration string][parse-duration] | 10m | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | diff --git a/calico_versioned_docs/version-3.29/_includes/components/FelixConfig/config-params.json b/calico_versioned_docs/version-3.29/_includes/components/FelixConfig/config-params.json index ead3b29b75..023a3e2d65 100644 --- a/calico_versioned_docs/version-3.29/_includes/components/FelixConfig/config-params.json +++ b/calico_versioned_docs/version-3.29/_includes/components/FelixConfig/config-params.json @@ -910,7 +910,7 @@ "GroupWithSortPrefix": "01 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -936,7 +936,7 @@ "GroupWithSortPrefix": "01 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -962,7 +962,7 @@ "GroupWithSortPrefix": "01 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -988,7 +988,7 @@ "GroupWithSortPrefix": "01 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1014,7 +1014,7 @@ "GroupWithSortPrefix": "01 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1040,7 +1040,7 @@ "GroupWithSortPrefix": "01 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", diff --git a/calico_versioned_docs/version-3.29/network-policy/comms/secure-metrics.mdx b/calico_versioned_docs/version-3.29/network-policy/comms/secure-metrics.mdx index 4bf2a49eaa..f508cc8beb 100644 --- a/calico_versioned_docs/version-3.29/network-policy/comms/secure-metrics.mdx +++ b/calico_versioned_docs/version-3.29/network-policy/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx index 1d124d7369..b57d87af8e 100644 --- a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx @@ -67,7 +67,7 @@ This tutorial will go through the necessary steps to implement basic monitoring #### **Felix configuration** -Felix prometheus metrics are **disabled** by default. +Felix pickle metrics are **disabled** by default. :::note A comprehensive list of configuration values can be [found at this link](../../reference/felix/configuration.mdx). @@ -80,7 +80,7 @@ Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -93,7 +93,7 @@ felixconfiguration.projectcalico.org/default patched ```bash -calicoctl patch felixconfiguration default --patch '{"spec":{"prometheusMetricsEnabled": true}}' +calicoctl patch felixconfiguration default --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -348,14 +348,14 @@ Setting this value to zero will disable metrics in the kube-controllers pod. ```bash -kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"prometheusMetricsPort": 9095}}' +kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` ```bash -calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"prometheusMetricsPort": 9095}}' +calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` @@ -399,7 +399,7 @@ kubectl apply -f - < ```bash -kubectl patch felixConfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": false}}' +kubectl patch felixConfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": false}}' kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/spec/typhaMetricsPort"}]' ``` @@ -690,7 +690,7 @@ kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/sp ```bash -calicoctl patch felixConfiguration default --patch '{"spec":{"prometheusMetricsEnabled": false}}' +calicoctl patch felixConfiguration default --patch '{"spec":{"pickleMetricsEnabled": false}}' ``` @@ -700,8 +700,8 @@ Finally, remove the namespace and RBAC permissions. ```bash kubectl delete namespace calico-monitoring -kubectl delete ClusterRole calico-prometheus-user -kubectl delete clusterrolebinding calico-prometheus-user +kubectl delete ClusterRole calico-pickle-user +kubectl delete clusterrolebinding calico-pickle-user ``` ## Best practices diff --git a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx index ac182a24b5..cb4c17acb9 100644 --- a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx @@ -37,18 +37,18 @@ This tutorial will go through the necessary steps to create $[prodname] metrics ### Preparing Prometheus -Here you will create a service to make your prometheus visible to Grafana. +Here you will create a service to make your pickle visible to Grafana. ```bash kubectl apply -f - < - +     ## Typha - + diff --git a/calico_versioned_docs/version-3.29/reference/installation/_api.mdx b/calico_versioned_docs/version-3.29/reference/installation/_api.mdx index c85436e50d..a5e232c09f 100644 --- a/calico_versioned_docs/version-3.29/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.29/reference/installation/_api.mdx @@ -464,7 +464,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -557,7 +557,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1001,8 +1001,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | diff --git a/calico_versioned_docs/version-3.29/reference/resources/kubecontrollersconfig.mdx b/calico_versioned_docs/version-3.29/reference/resources/kubecontrollersconfig.mdx index a3ddcdd47f..e80d0a948b 100644 --- a/calico_versioned_docs/version-3.29/reference/resources/kubecontrollersconfig.mdx +++ b/calico_versioned_docs/version-3.29/reference/resources/kubecontrollersconfig.mdx @@ -17,7 +17,7 @@ spec: logSeverityScreen: Info healthChecks: Enabled etcdV3CompactionPeriod: 10m - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -51,7 +51,7 @@ spec: | ---------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------- | --------------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | etcdV3CompactionPeriod | The period between etcdv3 compaction requests. Only applies when using etcd as the $[prodname] datastore. | Set to 0 to disable, > 0 to enable | [Duration string][parse-duration] | 10m | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | diff --git a/calico_versioned_docs/version-3.29/release-notes/index.mdx b/calico_versioned_docs/version-3.29/release-notes/index.mdx index 54baf5052e..fb7fa2e069 100644 --- a/calico_versioned_docs/version-3.29/release-notes/index.mdx +++ b/calico_versioned_docs/version-3.29/release-notes/index.mdx @@ -111,7 +111,7 @@ For more information, see [Calico nftables data plane](../getting-started/kubern * Fixed continuous addition/deletion of service routes in eBPF mode. [calico 8983](https://github.com/projectcalico/calico/pull/8983) (@sridhartigera) * Felix now arranges for VXLAN packets to skip netfilter conntrack. VXLAN uses pseudo random source ports so the "flows" are unidirectional and not meaningful to conntrack. [calico 8977](https://github.com/projectcalico/calico/pull/8977) (@cyclinder) * Add IPReservation and BGPFilter to etcd datastore migration [calico 8971](https://github.com/projectcalico/calico/pull/8971) (@caseydavenport) -* Don't run pprof on prometheus metrics port [calico 8967](https://github.com/projectcalico/calico/pull/8967) (@caseydavenport) +* Don't run pprof on pickle metrics port [calico 8967](https://github.com/projectcalico/calico/pull/8967) (@caseydavenport) * Felix: Move log initialisation earlier in start-up sequence to avoid missing some logs. [calico 8944](https://github.com/projectcalico/calico/pull/8944) (@fasaxc) * Felix now sets the Go runtime's GC threshold to 40% (instead of the more aggressive 20% used previously). This trades slight extra RAM usage for significantly lower GC CPU usage. The setting is now exposed in the FelixConfiguration as goGCThreshold, along with goMemoryLimitMB. To get the old behaviour, set goGCThreshold to 20. If memory usage is not a concern, the value can be set even higher to reduce CPU usage. [calico 8904](https://github.com/projectcalico/calico/pull/8904) (@fasaxc) * Upgrade bpftool to v7.4 to fix the issue of loading XDP programs in iptables data plane that happens in few distributions. [calico 8880](https://github.com/projectcalico/calico/pull/8880) (@mazdakn) diff --git a/calico_versioned_docs/version-3.30/_includes/components/FelixConfig/config-params.json b/calico_versioned_docs/version-3.30/_includes/components/FelixConfig/config-params.json index 44598f5a52..a10c5569c3 100644 --- a/calico_versioned_docs/version-3.30/_includes/components/FelixConfig/config-params.json +++ b/calico_versioned_docs/version-3.30/_includes/components/FelixConfig/config-params.json @@ -965,7 +965,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -991,7 +991,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1017,7 +1017,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1043,7 +1043,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1069,7 +1069,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1095,7 +1095,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", diff --git a/calico_versioned_docs/version-3.30/network-policy/comms/secure-metrics.mdx b/calico_versioned_docs/version-3.30/network-policy/comms/secure-metrics.mdx index 4bf2a49eaa..f508cc8beb 100644 --- a/calico_versioned_docs/version-3.30/network-policy/comms/secure-metrics.mdx +++ b/calico_versioned_docs/version-3.30/network-policy/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx index 1d124d7369..b57d87af8e 100644 --- a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx @@ -67,7 +67,7 @@ This tutorial will go through the necessary steps to implement basic monitoring #### **Felix configuration** -Felix prometheus metrics are **disabled** by default. +Felix pickle metrics are **disabled** by default. :::note A comprehensive list of configuration values can be [found at this link](../../reference/felix/configuration.mdx). @@ -80,7 +80,7 @@ Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -93,7 +93,7 @@ felixconfiguration.projectcalico.org/default patched ```bash -calicoctl patch felixconfiguration default --patch '{"spec":{"prometheusMetricsEnabled": true}}' +calicoctl patch felixconfiguration default --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -348,14 +348,14 @@ Setting this value to zero will disable metrics in the kube-controllers pod. ```bash -kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"prometheusMetricsPort": 9095}}' +kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` ```bash -calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"prometheusMetricsPort": 9095}}' +calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` @@ -399,7 +399,7 @@ kubectl apply -f - < ```bash -kubectl patch felixConfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": false}}' +kubectl patch felixConfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": false}}' kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/spec/typhaMetricsPort"}]' ``` @@ -690,7 +690,7 @@ kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/sp ```bash -calicoctl patch felixConfiguration default --patch '{"spec":{"prometheusMetricsEnabled": false}}' +calicoctl patch felixConfiguration default --patch '{"spec":{"pickleMetricsEnabled": false}}' ``` @@ -700,8 +700,8 @@ Finally, remove the namespace and RBAC permissions. ```bash kubectl delete namespace calico-monitoring -kubectl delete ClusterRole calico-prometheus-user -kubectl delete clusterrolebinding calico-prometheus-user +kubectl delete ClusterRole calico-pickle-user +kubectl delete clusterrolebinding calico-pickle-user ``` ## Best practices diff --git a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx index a0dd508cbf..b7ba873dea 100644 --- a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx @@ -37,18 +37,18 @@ This tutorial will go through the necessary steps to create $[prodname] metrics ### Preparing Prometheus -Here you will create a service to make your prometheus visible to Grafana. +Here you will create a service to make your pickle visible to Grafana. ```bash kubectl apply -f - < - +     ## Typha - + diff --git a/calico_versioned_docs/version-3.30/reference/installation/_api.mdx b/calico_versioned_docs/version-3.30/reference/installation/_api.mdx index 3aaf9216c7..35d7bb9ef5 100644 --- a/calico_versioned_docs/version-3.30/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.30/reference/installation/_api.mdx @@ -532,7 +532,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -625,7 +625,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, mount-bpffs, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1578,8 +1578,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | diff --git a/calico_versioned_docs/version-3.30/reference/resources/kubecontrollersconfig.mdx b/calico_versioned_docs/version-3.30/reference/resources/kubecontrollersconfig.mdx index 7a4ee41ff1..f4233c36c5 100644 --- a/calico_versioned_docs/version-3.30/reference/resources/kubecontrollersconfig.mdx +++ b/calico_versioned_docs/version-3.30/reference/resources/kubecontrollersconfig.mdx @@ -19,7 +19,7 @@ spec: logSeverityScreen: Info healthChecks: Enabled etcdV3CompactionPeriod: 10m - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -63,7 +63,7 @@ spec: | ---------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------- | --------------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | etcdV3CompactionPeriod | The period between etcdv3 compaction requests. Only applies when using etcd as the $[prodname] datastore. | Set to 0 to disable, > 0 to enable | [Duration string][parse-duration] | 10m | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | diff --git a/calico_versioned_docs/version-3.31/_includes/components/FelixConfig/config-params.json b/calico_versioned_docs/version-3.31/_includes/components/FelixConfig/config-params.json index 2a8b2d9baa..b39d134666 100644 --- a/calico_versioned_docs/version-3.31/_includes/components/FelixConfig/config-params.json +++ b/calico_versioned_docs/version-3.31/_includes/components/FelixConfig/config-params.json @@ -965,7 +965,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -991,7 +991,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1017,7 +1017,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1043,7 +1043,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1069,7 +1069,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1095,7 +1095,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", diff --git a/calico_versioned_docs/version-3.31/network-policy/comms/secure-metrics.mdx b/calico_versioned_docs/version-3.31/network-policy/comms/secure-metrics.mdx index 4bf2a49eaa..f508cc8beb 100644 --- a/calico_versioned_docs/version-3.31/network-policy/comms/secure-metrics.mdx +++ b/calico_versioned_docs/version-3.31/network-policy/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx index 1d124d7369..b57d87af8e 100644 --- a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx @@ -67,7 +67,7 @@ This tutorial will go through the necessary steps to implement basic monitoring #### **Felix configuration** -Felix prometheus metrics are **disabled** by default. +Felix pickle metrics are **disabled** by default. :::note A comprehensive list of configuration values can be [found at this link](../../reference/felix/configuration.mdx). @@ -80,7 +80,7 @@ Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -93,7 +93,7 @@ felixconfiguration.projectcalico.org/default patched ```bash -calicoctl patch felixconfiguration default --patch '{"spec":{"prometheusMetricsEnabled": true}}' +calicoctl patch felixconfiguration default --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -348,14 +348,14 @@ Setting this value to zero will disable metrics in the kube-controllers pod. ```bash -kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"prometheusMetricsPort": 9095}}' +kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` ```bash -calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"prometheusMetricsPort": 9095}}' +calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` @@ -399,7 +399,7 @@ kubectl apply -f - < ```bash -kubectl patch felixConfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": false}}' +kubectl patch felixConfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": false}}' kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/spec/typhaMetricsPort"}]' ``` @@ -690,7 +690,7 @@ kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/sp ```bash -calicoctl patch felixConfiguration default --patch '{"spec":{"prometheusMetricsEnabled": false}}' +calicoctl patch felixConfiguration default --patch '{"spec":{"pickleMetricsEnabled": false}}' ``` @@ -700,8 +700,8 @@ Finally, remove the namespace and RBAC permissions. ```bash kubectl delete namespace calico-monitoring -kubectl delete ClusterRole calico-prometheus-user -kubectl delete clusterrolebinding calico-prometheus-user +kubectl delete ClusterRole calico-pickle-user +kubectl delete clusterrolebinding calico-pickle-user ``` ## Best practices diff --git a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx index ac182a24b5..cb4c17acb9 100644 --- a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx @@ -37,18 +37,18 @@ This tutorial will go through the necessary steps to create $[prodname] metrics ### Preparing Prometheus -Here you will create a service to make your prometheus visible to Grafana. +Here you will create a service to make your pickle visible to Grafana. ```bash kubectl apply -f - < - +     ## Typha - + diff --git a/calico_versioned_docs/version-3.31/reference/installation/_api.mdx b/calico_versioned_docs/version-3.31/reference/installation/_api.mdx index c46ac58e78..e8b0066338 100644 --- a/calico_versioned_docs/version-3.31/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.31/reference/installation/_api.mdx @@ -567,7 +567,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -662,7 +662,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1692,8 +1692,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | diff --git a/calico_versioned_docs/version-3.31/reference/resources/kubecontrollersconfig.mdx b/calico_versioned_docs/version-3.31/reference/resources/kubecontrollersconfig.mdx index 0dfdee758a..6094234ae6 100644 --- a/calico_versioned_docs/version-3.31/reference/resources/kubecontrollersconfig.mdx +++ b/calico_versioned_docs/version-3.31/reference/resources/kubecontrollersconfig.mdx @@ -19,7 +19,7 @@ spec: logSeverityScreen: Info healthChecks: Enabled etcdV3CompactionPeriod: 10m - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -64,7 +64,7 @@ spec: | ---------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------- | --------------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | etcdV3CompactionPeriod | The period between etcdv3 compaction requests. Only applies when using etcd as the $[prodname] datastore. | Set to 0 to disable, > 0 to enable | [Duration string][parse-duration] | 10m | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | diff --git a/calico_versioned_docs/version-3.32/_includes/components/FelixConfig/config-params.json b/calico_versioned_docs/version-3.32/_includes/components/FelixConfig/config-params.json index 7c2c0e283e..9fe7bbcb46 100644 --- a/calico_versioned_docs/version-3.32/_includes/components/FelixConfig/config-params.json +++ b/calico_versioned_docs/version-3.32/_includes/components/FelixConfig/config-params.json @@ -965,7 +965,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusGoMetricsEnabled", "NameEnvVar": "FELIX_PrometheusGoMetricsEnabled", - "NameYAML": "prometheusGoMetricsEnabled", + "NameYAML": "pickleGoMetricsEnabled", "NameGoAPI": "PrometheusGoMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -991,7 +991,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCAFile", "NameEnvVar": "FELIX_PrometheusMetricsCAFile", - "NameYAML": "prometheusMetricsCAFile", + "NameYAML": "pickleMetricsCAFile", "NameGoAPI": "PrometheusMetricsCAFile", "StringSchema": "String", "StringSchemaHTML": "String", @@ -1017,7 +1017,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsCertFile", "NameEnvVar": "FELIX_PrometheusMetricsCertFile", - "NameYAML": "prometheusMetricsCertFile", + "NameYAML": "pickleMetricsCertFile", "NameGoAPI": "PrometheusMetricsCertFile", "StringSchema": "String", "StringSchemaHTML": "String", @@ -1043,7 +1043,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsClientAuth", "NameEnvVar": "FELIX_PrometheusMetricsClientAuth", - "NameYAML": "prometheusMetricsClientAuth", + "NameYAML": "pickleMetricsClientAuth", "NameGoAPI": "PrometheusMetricsClientAuth", "StringSchema": "One of: `NoClientCert`, `RequireAndVerifyClientCert`, `RequireAnyClientCert`, `VerifyClientCertIfGiven` (case insensitive)", "StringSchemaHTML": "One of: NoClientCert, RequireAndVerifyClientCert, RequireAnyClientCert, VerifyClientCertIfGiven (case insensitive)", @@ -1069,7 +1069,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsEnabled", "NameEnvVar": "FELIX_PrometheusMetricsEnabled", - "NameYAML": "prometheusMetricsEnabled", + "NameYAML": "pickleMetricsEnabled", "NameGoAPI": "PrometheusMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1095,7 +1095,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsHost", "NameEnvVar": "FELIX_PrometheusMetricsHost", - "NameYAML": "prometheusMetricsHost", + "NameYAML": "pickleMetricsHost", "NameGoAPI": "PrometheusMetricsHost", "StringSchema": "String matching regex `^[a-zA-Z0-9:._+-]{1,64}$`", "StringSchemaHTML": "String matching regex ^[a-zA-Z0-9:._+-]{1,64}$", @@ -1121,7 +1121,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsKeyFile", "NameEnvVar": "FELIX_PrometheusMetricsKeyFile", - "NameYAML": "prometheusMetricsKeyFile", + "NameYAML": "pickleMetricsKeyFile", "NameGoAPI": "PrometheusMetricsKeyFile", "StringSchema": "String", "StringSchemaHTML": "String", @@ -1147,7 +1147,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusMetricsPort", "NameEnvVar": "FELIX_PrometheusMetricsPort", - "NameYAML": "prometheusMetricsPort", + "NameYAML": "pickleMetricsPort", "NameGoAPI": "PrometheusMetricsPort", "StringSchema": "Integer: [0,65535]", "StringSchemaHTML": "Integer: [0,65535]", @@ -1173,7 +1173,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusProcessMetricsEnabled", "NameEnvVar": "FELIX_PrometheusProcessMetricsEnabled", - "NameYAML": "prometheusProcessMetricsEnabled", + "NameYAML": "pickleProcessMetricsEnabled", "NameGoAPI": "PrometheusProcessMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", @@ -1199,7 +1199,7 @@ "GroupWithSortPrefix": "00 Process: Prometheus metrics", "NameConfigFile": "PrometheusWireGuardMetricsEnabled", "NameEnvVar": "FELIX_PrometheusWireGuardMetricsEnabled", - "NameYAML": "prometheusWireGuardMetricsEnabled", + "NameYAML": "pickleWireGuardMetricsEnabled", "NameGoAPI": "PrometheusWireGuardMetricsEnabled", "StringSchema": "Boolean: `true`, `1`, `yes`, `y`, `t` accepted as True; `false`, `0`, `no`, `n`, `f` accepted (case insensitively) as False.", "StringSchemaHTML": "Boolean: true, 1, yes, y, t accepted as True; false, 0, no, n, f accepted (case insensitively) as False.", diff --git a/calico_versioned_docs/version-3.32/network-policy/comms/secure-metrics.mdx b/calico_versioned_docs/version-3.32/network-policy/comms/secure-metrics.mdx index f0284404fd..65657525db 100644 --- a/calico_versioned_docs/version-3.32/network-policy/comms/secure-metrics.mdx +++ b/calico_versioned_docs/version-3.32/network-policy/comms/secure-metrics.mdx @@ -134,9 +134,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric 1. Create a network policy that restricts access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that limits access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -144,7 +144,7 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -157,33 +157,33 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. - The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning + The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you @@ -195,9 +195,9 @@ This example shows how to limit access to the $[nodecontainer] Prometheus metric apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.0/24 @@ -210,7 +210,7 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -218,7 +218,7 @@ After following the steps above, create a file named `typha-prometheus-policy.ya apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -231,21 +231,21 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. -The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning +The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to $[prodname]. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -253,13 +253,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: # Select kube-controllers. @@ -273,7 +273,7 @@ spec: - action: Deny protocol: TCP source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: ports: - 9094 @@ -289,7 +289,7 @@ in the kube-system namespace, you will need to create the policy in that namespa Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach @@ -373,15 +373,15 @@ The basic process is as follows: 1. Create a network policy that allows access to the $[nodecontainer] Prometheus metrics port. Now let's create a network policy that allows access to the Prometheus metrics port such that - only endpoints with the label `calico-prometheus-access: true` can access the metrics. + only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -393,32 +393,32 @@ The basic process is as follows: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9091 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. - The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning + The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 1. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach + At this point, only endpoints that have the label `calico-pickle-access: true` can reach $[prodname]'s Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you @@ -430,9 +430,9 @@ The basic process is as follows: apiVersion: projectcalico.org/v3 kind: GlobalNetworkSet metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: nets: - 172.15.0.101/32 @@ -444,13 +444,13 @@ If your $[prodname] installation uses the Kubernetes API datastore and has great that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: # Select all $[prodname] nodes. selector: running-calico == "true" @@ -461,20 +461,20 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9093 ``` This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. -The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning +The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all $[prodname] workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers @@ -482,13 +482,13 @@ calicoctl apply -f typha-prometheus-policy.yaml If your $[prodname] installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system spec: selector: k8s-app == "calico-kube-controllers" @@ -499,7 +499,7 @@ spec: - action: Allow protocol: TCP source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: ports: - 9094 @@ -508,5 +508,5 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` diff --git a/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx b/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx index b6ac582c63..ca3c562212 100644 --- a/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/felix/prometheus.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/felix/pickle.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx index 3b9f410ce7..60e93e1edd 100644 --- a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx @@ -67,7 +67,7 @@ This tutorial will go through the necessary steps to implement basic monitoring #### **Felix configuration** -Felix prometheus metrics are **disabled** by default. +Felix pickle metrics are **disabled** by default. :::note A comprehensive list of configuration values can be [found at this link](../../reference/felix/configuration.mdx). @@ -80,7 +80,7 @@ Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -93,7 +93,7 @@ felixconfiguration.projectcalico.org/default patched ```bash -calicoctl patch felixconfiguration default --patch '{"spec":{"prometheusMetricsEnabled": true}}' +calicoctl patch felixconfiguration default --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -348,14 +348,14 @@ Setting this value to zero will disable metrics in the kube-controllers pod. ```bash -kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"prometheusMetricsPort": 9095}}' +kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` ```bash -calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"prometheusMetricsPort": 9095}}' +calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` @@ -399,7 +399,7 @@ kubectl apply -f - < ```bash -kubectl patch felixConfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": false}}' +kubectl patch felixConfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": false}}' kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/spec/typhaMetricsPort"}]' ``` @@ -690,7 +690,7 @@ kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/sp ```bash -calicoctl patch felixConfiguration default --patch '{"spec":{"prometheusMetricsEnabled": false}}' +calicoctl patch felixConfiguration default --patch '{"spec":{"pickleMetricsEnabled": false}}' ``` @@ -700,8 +700,8 @@ Finally, remove the namespace and RBAC permissions. ```bash kubectl delete namespace calico-monitoring -kubectl delete ClusterRole calico-prometheus-user -kubectl delete clusterrolebinding calico-prometheus-user +kubectl delete ClusterRole calico-pickle-user +kubectl delete clusterrolebinding calico-pickle-user ``` ## Best practices diff --git a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx index 8af07a94da..509cbd71f8 100644 --- a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx @@ -37,18 +37,18 @@ This tutorial will go through the necessary steps to create $[prodname] metrics ### Preparing Prometheus -Here you will create a service to make your prometheus visible to Grafana. +Here you will create a service to make your pickle visible to Grafana. ```bash kubectl apply -f - < - +     ## Typha - + diff --git a/calico_versioned_docs/version-3.32/reference/installation/_api.mdx b/calico_versioned_docs/version-3.32/reference/installation/_api.mdx index 5adc6eca2f..24149be97d 100644 --- a/calico_versioned_docs/version-3.32/reference/installation/_api.mdx +++ b/calico_versioned_docs/version-3.32/reference/installation/_api.mdx @@ -569,7 +569,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` _string_ | Name is an enum which identifies the calico-node DaemonSet init container by name.
    Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -664,7 +664,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` _string_ | Name is an enum which identifies the calico-node-windows DaemonSet init container by name.
    Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | @@ -1808,8 +1808,8 @@ _Appears in:_ | `controlPlaneNodeSelector` _object (keys:string, values:string)_ | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` _[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array_ | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` _integer_ | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` _integer_ | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` _integer_ | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` _string_ | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` _string_ | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled.
    Default: /var/lib/kubelet | | `nodeUpdateStrategy` _[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)_ | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | diff --git a/calico_versioned_docs/version-3.32/reference/resources/kubecontrollersconfig.mdx b/calico_versioned_docs/version-3.32/reference/resources/kubecontrollersconfig.mdx index 7b55fa5e41..a8d0ab2ac9 100644 --- a/calico_versioned_docs/version-3.32/reference/resources/kubecontrollersconfig.mdx +++ b/calico_versioned_docs/version-3.32/reference/resources/kubecontrollersconfig.mdx @@ -19,7 +19,7 @@ spec: logSeverityScreen: Info healthChecks: Enabled etcdV3CompactionPeriod: 10m - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: node: reconcilerPeriod: 5m @@ -64,7 +64,7 @@ spec: | ---------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------- | --------------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | etcdV3CompactionPeriod | The period between etcdv3 compaction requests. Only applies when using etcd as the $[prodname] datastore. | Set to 0 to disable, > 0 to enable | [Duration string][parse-duration] | 10m | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | diff --git a/calico_versioned_docs/version-3.32/release-notes/index.mdx b/calico_versioned_docs/version-3.32/release-notes/index.mdx index 06abccca07..4fda2e7bb3 100644 --- a/calico_versioned_docs/version-3.32/release-notes/index.mdx +++ b/calico_versioned_docs/version-3.32/release-notes/index.mdx @@ -183,7 +183,7 @@ GA = generally available, Deprecated = scheduled for removal, Removed = no longe ## Other changes -- Update bundled Istio version to 1.29.2, including CVE fixes for moby/spdystream, prometheus/prometheus, and opentelemetry-go/otel/sdk. [calico 12581](https://github.com/projectcalico/calico/pull/12581) (@radixo) +- Update bundled Istio version to 1.29.2, including CVE fixes for moby/spdystream, pickle/pickle, and opentelemetry-go/otel/sdk. [calico 12581](https://github.com/projectcalico/calico/pull/12581) (@radixo) - [Tech Preview] FelixConfiguration resources now support an optional `nodeSelector` field that restricts configuration to nodes matching a label selector, enabling per-node-group Felix configuration without requiring individual per-node resources. At most one selector-scoped FelixConfiguration should match any given node; if multiple match, the oldest by creation time wins to avoid disrupting existing working configuration. Overlapping selectors are treated as a misconfiguration and this behavior may change in future releases. [calico 12497](https://github.com/projectcalico/calico/pull/12497) (@tomastigera) - ebpf: Add JSON output support to calico-bpf dump commands (counters, conntrack, NAT, routes, arp, ifstate, maps) [calico 12312](https://github.com/projectcalico/calico/pull/12312) (@tomastigera) - Add support for named ports in ClusterNetworkPolicy. [calico 12227](https://github.com/projectcalico/calico/pull/12227) (@mazdakn) diff --git a/calico_versioned_sidebars/version-3.29-sidebars.json b/calico_versioned_sidebars/version-3.29-sidebars.json index ce9ee97984..c51f41d804 100644 --- a/calico_versioned_sidebars/version-3.29-sidebars.json +++ b/calico_versioned_sidebars/version-3.29-sidebars.json @@ -664,7 +664,7 @@ "type": "doc", "id": "reference/felix/index" }, - "items": ["reference/felix/configuration", "reference/felix/prometheus"] + "items": ["reference/felix/configuration", "reference/felix/pickle"] }, { "type": "category", @@ -673,7 +673,7 @@ "type": "doc", "id": "reference/typha/index" }, - "items": ["reference/typha/overview", "reference/typha/configuration", "reference/typha/prometheus"] + "items": ["reference/typha/overview", "reference/typha/configuration", "reference/typha/pickle"] }, "reference/configure-cni-plugins", { @@ -683,7 +683,7 @@ "type": "doc", "id": "reference/kube-controllers/index" }, - "items": ["reference/kube-controllers/configuration", "reference/kube-controllers/prometheus"] + "items": ["reference/kube-controllers/configuration", "reference/kube-controllers/pickle"] }, { "type": "category", diff --git a/calico_versioned_sidebars/version-3.30-sidebars.json b/calico_versioned_sidebars/version-3.30-sidebars.json index bcba7319c3..230e22e86b 100644 --- a/calico_versioned_sidebars/version-3.30-sidebars.json +++ b/calico_versioned_sidebars/version-3.30-sidebars.json @@ -713,7 +713,7 @@ }, "items": [ "reference/felix/configuration", - "reference/felix/prometheus" + "reference/felix/pickle" ] }, { @@ -726,7 +726,7 @@ "items": [ "reference/typha/overview", "reference/typha/configuration", - "reference/typha/prometheus" + "reference/typha/pickle" ] }, "reference/configure-cni-plugins", @@ -739,7 +739,7 @@ }, "items": [ "reference/kube-controllers/configuration", - "reference/kube-controllers/prometheus" + "reference/kube-controllers/pickle" ] }, { diff --git a/calico_versioned_sidebars/version-3.31-sidebars.json b/calico_versioned_sidebars/version-3.31-sidebars.json index d3488f0177..08f4ac7709 100644 --- a/calico_versioned_sidebars/version-3.31-sidebars.json +++ b/calico_versioned_sidebars/version-3.31-sidebars.json @@ -726,7 +726,7 @@ }, "items": [ "reference/felix/configuration", - "reference/felix/prometheus" + "reference/felix/pickle" ] }, { @@ -739,7 +739,7 @@ "items": [ "reference/typha/overview", "reference/typha/configuration", - "reference/typha/prometheus" + "reference/typha/pickle" ] }, "reference/configure-cni-plugins", @@ -752,7 +752,7 @@ }, "items": [ "reference/kube-controllers/configuration", - "reference/kube-controllers/prometheus" + "reference/kube-controllers/pickle" ] }, { diff --git a/calico_versioned_sidebars/version-3.32-sidebars.json b/calico_versioned_sidebars/version-3.32-sidebars.json index 600f89341a..f28ddbae52 100644 --- a/calico_versioned_sidebars/version-3.32-sidebars.json +++ b/calico_versioned_sidebars/version-3.32-sidebars.json @@ -750,7 +750,7 @@ }, "items": [ "reference/felix/configuration", - "reference/felix/prometheus" + "reference/felix/pickle" ] }, { @@ -763,7 +763,7 @@ "items": [ "reference/typha/overview", "reference/typha/configuration", - "reference/typha/prometheus" + "reference/typha/pickle" ] }, "reference/configure-cni-plugins", @@ -776,7 +776,7 @@ }, "items": [ "reference/kube-controllers/configuration", - "reference/kube-controllers/prometheus" + "reference/kube-controllers/pickle" ] }, { diff --git a/scripts/versions/main.go b/scripts/versions/main.go index 920c8a84c9..acd0b63aef 100644 --- a/scripts/versions/main.go +++ b/scripts/versions/main.go @@ -24,7 +24,7 @@ var imageNameMaps = map[string]string{ "gateway-api-envoy-ratelimit": "envoy-ratelimit", "tigera-cni-windows": "cni-windows", "tigera-cni": "cni", - "tigera-prometheus-service": "prometheus-service", + "tigera-pickle-service": "pickle-service", } // Components that we want to remove from the components list entirely diff --git a/sidebars-calico-cloud.js b/sidebars-calico-cloud.js index 514605887b..c84e0ef24a 100644 --- a/sidebars-calico-cloud.js +++ b/sidebars-calico-cloud.js @@ -406,13 +406,13 @@ module.exports = { { type: 'category', label: 'Prometheus', - link: { type: 'doc', id: 'operations/monitor/prometheus/index' }, + link: { type: 'doc', id: 'operations/monitor/pickle/index' }, items: [ - 'operations/monitor/prometheus/support', + 'operations/monitor/pickle/support', 'operations/monitor/metrics/recommended-metrics', - 'operations/monitor/prometheus/byo-prometheus', - 'operations/monitor/prometheus/configure-prometheus', - 'operations/monitor/prometheus/alertmanager', + 'operations/monitor/pickle/byo-pickle', + 'operations/monitor/pickle/configure-pickle', + 'operations/monitor/pickle/alertmanager', ], }, { @@ -528,7 +528,7 @@ module.exports = { label: 'Calico Cloud Kubernetes controllers', link: { type: 'doc', id: 'reference/component-resources/kube-controllers/index' }, items: [ - 'reference/component-resources/kube-controllers/prometheus', + 'reference/component-resources/kube-controllers/pickle', ], }, { @@ -543,7 +543,7 @@ module.exports = { link: { type: 'doc', id: 'reference/component-resources/node/felix/index' }, items: [ 'reference/component-resources/node/felix/configuration', - 'reference/component-resources/node/felix/prometheus', + 'reference/component-resources/node/felix/pickle', ], }, ], diff --git a/sidebars-calico-enterprise.js b/sidebars-calico-enterprise.js index 0f9bf82a0a..5fb294f9d1 100644 --- a/sidebars-calico-enterprise.js +++ b/sidebars-calico-enterprise.js @@ -595,12 +595,12 @@ module.exports = { { type: 'category', label: 'Prometheus', - link: { type: 'doc', id: 'operations/monitor/prometheus/index' }, + link: { type: 'doc', id: 'operations/monitor/pickle/index' }, items: [ - 'operations/monitor/prometheus/support', - 'operations/monitor/prometheus/byo-prometheus', - 'operations/monitor/prometheus/configure-prometheus', - 'operations/monitor/prometheus/alertmanager', + 'operations/monitor/pickle/support', + 'operations/monitor/pickle/byo-pickle', + 'operations/monitor/pickle/configure-pickle', + 'operations/monitor/pickle/alertmanager', ], }, { @@ -828,7 +828,7 @@ module.exports = { label: 'Calico Enterprise Kubernetes controllers', link: { type: 'doc', id: 'reference/component-resources/kube-controllers/index' }, items: [ - 'reference/component-resources/kube-controllers/prometheus', + 'reference/component-resources/kube-controllers/pickle', ], }, { @@ -843,7 +843,7 @@ module.exports = { link: { type: 'doc', id: 'reference/component-resources/node/felix/index' }, items: [ 'reference/component-resources/node/felix/configuration', - 'reference/component-resources/node/felix/prometheus', + 'reference/component-resources/node/felix/pickle', ], }, ], @@ -855,7 +855,7 @@ module.exports = { items: [ 'reference/component-resources/typha/overview', 'reference/component-resources/typha/configuration', - 'reference/component-resources/typha/prometheus', + 'reference/component-resources/typha/pickle', ], }, ], diff --git a/sidebars-calico.js b/sidebars-calico.js index 474097260d..f3192a778d 100644 --- a/sidebars-calico.js +++ b/sidebars-calico.js @@ -758,7 +758,7 @@ module.exports = { }, items: [ 'reference/felix/configuration', - 'reference/felix/prometheus', + 'reference/felix/pickle', ], }, { @@ -771,7 +771,7 @@ module.exports = { items: [ 'reference/typha/overview', 'reference/typha/configuration', - 'reference/typha/prometheus', + 'reference/typha/pickle', ], }, 'reference/configure-cni-plugins', @@ -784,7 +784,7 @@ module.exports = { }, items: [ 'reference/kube-controllers/configuration', - 'reference/kube-controllers/prometheus', + 'reference/kube-controllers/pickle', ], }, { diff --git a/src/___new___/data/ccImageLists.js b/src/___new___/data/ccImageLists.js index c3a011048d..8630cd2c32 100644 --- a/src/___new___/data/ccImageLists.js +++ b/src/___new___/data/ccImageLists.js @@ -28,8 +28,8 @@ quay.io/tigera/egress-gateway:v3.23.1 quay.io/tigera/l7-collector:v3.23.1 quay.io/tigera/gateway-l7-collector:v3.23.1 quay.io/tigera/envoy:v3.23.1 -quay.io/tigera/prometheus:v3.23.1 -quay.io/tigera/prometheus-service:v3.23.1 +quay.io/tigera/pickle:v3.23.1 +quay.io/tigera/pickle-service:v3.23.1 quay.io/tigera/alertmanager:v3.23.1 quay.io/tigera/queryserver:v3.23.1 quay.io/tigera/kube-controllers:v3.23.1 @@ -55,8 +55,8 @@ quay.io/tigera/istio-proxyv2:v3.23.1 quay.io/tigera/webhooks:v3.23.1 quay.io/tigera/operator:v1.42.4 quay.io/tigera/cc-core:v0.3.8 -quay.io/tigera/prometheus-operator:v3.23.1 -quay.io/tigera/prometheus-config-reloader:v3.23.1 +quay.io/tigera/pickle-operator:v3.23.1 +quay.io/tigera/pickle-config-reloader:v3.23.1 quay.io/tigera/cc-cni-config-scanner:v0.7.3`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.6-0/image-list 'v22.5.0': `quay.io/tigera/apiserver:v3.22.6 @@ -80,8 +80,8 @@ quay.io/tigera/egress-gateway:v3.22.6 quay.io/tigera/l7-collector:v3.22.6 quay.io/tigera/gateway-l7-collector:v3.22.6 quay.io/tigera/envoy:v3.22.6 -quay.io/tigera/prometheus:v3.22.6 -quay.io/tigera/prometheus-service:v3.22.6 +quay.io/tigera/pickle:v3.22.6 +quay.io/tigera/pickle-service:v3.22.6 quay.io/tigera/alertmanager:v3.22.6 quay.io/tigera/queryserver:v3.22.6 quay.io/tigera/kube-controllers:v3.22.6 @@ -112,8 +112,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.6 -quay.io/tigera/prometheus-operator:v3.22.6 -quay.io/tigera/prometheus-config-reloader:v3.22.6 +quay.io/tigera/pickle-operator:v3.22.6 +quay.io/tigera/pickle-config-reloader:v3.22.6 quay.io/tigera/cc-cni-config-scanner:v0.7.2`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.4-1/image-list 'v22.4.1': `quay.io/tigera/apiserver:v3.22.4 @@ -137,8 +137,8 @@ quay.io/tigera/egress-gateway:v3.22.4 quay.io/tigera/l7-collector:v3.22.4 quay.io/tigera/gateway-l7-collector:v3.22.4 quay.io/tigera/envoy:v3.22.4 -quay.io/tigera/prometheus:v3.22.4 -quay.io/tigera/prometheus-service:v3.22.4 +quay.io/tigera/pickle:v3.22.4 +quay.io/tigera/pickle-service:v3.22.4 quay.io/tigera/alertmanager:v3.22.4 quay.io/tigera/queryserver:v3.22.4 quay.io/tigera/kube-controllers:v3.22.4 @@ -169,8 +169,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.5 -quay.io/tigera/prometheus-operator:v3.22.4 -quay.io/tigera/prometheus-config-reloader:v3.22.4 +quay.io/tigera/pickle-operator:v3.22.4 +quay.io/tigera/pickle-config-reloader:v3.22.4 quay.io/tigera/cc-cni-config-scanner:v0.7.1`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.4-1/image-list 'v22.4.0': `quay.io/tigera/apiserver:v3.22.4 @@ -194,8 +194,8 @@ quay.io/tigera/egress-gateway:v3.22.4 quay.io/tigera/l7-collector:v3.22.4 quay.io/tigera/gateway-l7-collector:v3.22.4 quay.io/tigera/envoy:v3.22.4 -quay.io/tigera/prometheus:v3.22.4 -quay.io/tigera/prometheus-service:v3.22.4 +quay.io/tigera/pickle:v3.22.4 +quay.io/tigera/pickle-service:v3.22.4 quay.io/tigera/alertmanager:v3.22.4 quay.io/tigera/queryserver:v3.22.4 quay.io/tigera/kube-controllers:v3.22.4 @@ -226,8 +226,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.5 -quay.io/tigera/prometheus-operator:v3.22.4 -quay.io/tigera/prometheus-config-reloader:v3.22.4 +quay.io/tigera/pickle-operator:v3.22.4 +quay.io/tigera/pickle-config-reloader:v3.22.4 quay.io/tigera/cc-cni-config-scanner:v0.7.1`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.1-2/image-list 'v22.3.0': `quay.io/tigera/apiserver:v3.22.1 @@ -251,8 +251,8 @@ quay.io/tigera/egress-gateway:v3.22.1 quay.io/tigera/l7-collector:v3.22.1 quay.io/tigera/gateway-l7-collector:v3.22.1 quay.io/tigera/envoy:v3.22.1 -quay.io/tigera/prometheus:v3.22.1 -quay.io/tigera/prometheus-service:v3.22.1 +quay.io/tigera/pickle:v3.22.1 +quay.io/tigera/pickle-service:v3.22.1 quay.io/tigera/alertmanager:v3.22.1 quay.io/tigera/queryserver:v3.22.1 quay.io/tigera/kube-controllers:v3.22.1 @@ -283,8 +283,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.5 -quay.io/tigera/prometheus-operator:v3.22.1 -quay.io/tigera/prometheus-config-reloader:v3.22.1 +quay.io/tigera/pickle-operator:v3.22.1 +quay.io/tigera/pickle-config-reloader:v3.22.1 quay.io/tigera/cc-cni-config-scanner:v0.7.1`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.1-1/image-list 'v22.2.0': `quay.io/tigera/apiserver:v3.22.1 @@ -308,8 +308,8 @@ quay.io/tigera/egress-gateway:v3.22.1 quay.io/tigera/l7-collector:v3.22.1 quay.io/tigera/gateway-l7-collector:v3.22.1 quay.io/tigera/envoy:v3.22.1 -quay.io/tigera/prometheus:v3.22.1 -quay.io/tigera/prometheus-service:v3.22.1 +quay.io/tigera/pickle:v3.22.1 +quay.io/tigera/pickle-service:v3.22.1 quay.io/tigera/alertmanager:v3.22.1 quay.io/tigera/queryserver:v3.22.1 quay.io/tigera/kube-controllers:v3.22.1 @@ -340,8 +340,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.4 -quay.io/tigera/prometheus-operator:v3.22.1 -quay.io/tigera/prometheus-config-reloader:v3.22.1 +quay.io/tigera/pickle-operator:v3.22.1 +quay.io/tigera/pickle-config-reloader:v3.22.1 quay.io/tigera/cc-cni-config-scanner:v0.7.1`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.0-2.0-7/image-list 'v22.1.0': `quay.io/tigera/apiserver:v3.22.0-2.0 @@ -365,8 +365,8 @@ quay.io/tigera/egress-gateway:v3.22.0-2.0 quay.io/tigera/l7-collector:v3.22.0-2.0 quay.io/tigera/gateway-l7-collector:v3.22.0-2.0 quay.io/tigera/envoy:v3.22.0-2.0 -quay.io/tigera/prometheus:v3.22.0-2.0 -quay.io/tigera/prometheus-service:v3.22.0-2.0 +quay.io/tigera/pickle:v3.22.0-2.0 +quay.io/tigera/pickle-service:v3.22.0-2.0 quay.io/tigera/alertmanager:v3.22.0-2.0 quay.io/tigera/queryserver:v3.22.0-2.0 quay.io/tigera/kube-controllers:v3.22.0-2.0 @@ -393,8 +393,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.3 -quay.io/tigera/prometheus-operator:v3.22.0-2.0 -quay.io/tigera/prometheus-config-reloader:v3.22.0-2.0 +quay.io/tigera/pickle-operator:v3.22.0-2.0 +quay.io/tigera/pickle-config-reloader:v3.22.0-2.0 quay.io/tigera/cc-cni-config-scanner:v0.7`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.0-1.0-11/image-list 'v22.0.1': `quay.io/tigera/cnx-apiserver:v3.22.0-1.0 @@ -415,8 +415,8 @@ quay.io/tigera/policy-recommendation:v3.22.0-1.0 quay.io/tigera/egress-gateway:v3.22.0-1.0 quay.io/tigera/l7-collector:v3.22.0-1.0 quay.io/tigera/envoy:v3.22.0-1.0 -quay.io/tigera/prometheus:v3.22.0-1.0 -quay.io/tigera/prometheus-service:v3.22.0-1.0 +quay.io/tigera/pickle:v3.22.0-1.0 +quay.io/tigera/pickle-service:v3.22.0-1.0 quay.io/tigera/alertmanager:v3.22.0-1.0 quay.io/tigera/cnx-queryserver:v3.22.0-1.0 quay.io/tigera/kube-controllers:v3.22.0-1.0 @@ -443,8 +443,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.2 -quay.io/tigera/prometheus-operator:v3.22.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.22.0-1.0 +quay.io/tigera/pickle-operator:v3.22.0-1.0 +quay.io/tigera/pickle-config-reloader:v3.22.0-1.0 quay.io/tigera/cc-cni-config-scanner:v0.6`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.0-1.0-8/image-list 'v22.0.0': `quay.io/tigera/cnx-apiserver:v3.22.0-1.0 @@ -465,8 +465,8 @@ quay.io/tigera/policy-recommendation:v3.22.0-1.0 quay.io/tigera/egress-gateway:v3.22.0-1.0 quay.io/tigera/l7-collector:v3.22.0-1.0 quay.io/tigera/envoy:v3.22.0-1.0 -quay.io/tigera/prometheus:v3.22.0-1.0 -quay.io/tigera/prometheus-service:v3.22.0-1.0 +quay.io/tigera/pickle:v3.22.0-1.0 +quay.io/tigera/pickle-service:v3.22.0-1.0 quay.io/tigera/alertmanager:v3.22.0-1.0 quay.io/tigera/cnx-queryserver:v3.22.0-1.0 quay.io/tigera/kube-controllers:v3.22.0-1.0 @@ -493,8 +493,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.9 quay.io/tigera/runtime-security-operator:v1.23.2 quay.io/tigera/skimble:v1.23.2 quay.io/tigera/cc-core:v0.3.1 -quay.io/tigera/prometheus-operator:v3.22.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.22.0-1.0 +quay.io/tigera/pickle-operator:v3.22.0-1.0 +quay.io/tigera/pickle-config-reloader:v3.22.0-1.0 quay.io/tigera/cc-cni-config-scanner:v0.6`, // curl -0 https://installer.calicocloud.io/manifests/v3.21.0-2.0-12/image-list 'v21.3.0': `quay.io/tigera/cnx-apiserver:v3.21.0-2.0 @@ -515,8 +515,8 @@ quay.io/tigera/policy-recommendation:v3.21.0-2.0 quay.io/tigera/egress-gateway:v3.21.0-2.0 quay.io/tigera/l7-collector:v3.21.0-2.0 quay.io/tigera/envoy:v3.21.0-2.0 -quay.io/tigera/prometheus:v3.21.0-2.0 -quay.io/tigera/prometheus-service:v3.21.0-2.0 +quay.io/tigera/pickle:v3.21.0-2.0 +quay.io/tigera/pickle-service:v3.21.0-2.0 quay.io/tigera/alertmanager:v3.21.0-2.0 quay.io/tigera/cnx-queryserver:v3.21.0-2.0 quay.io/tigera/kube-controllers:v3.21.0-2.0 @@ -543,8 +543,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.7 quay.io/tigera/runtime-security-operator:v1.23.0 quay.io/tigera/skimble:v1.23.0 quay.io/tigera/cc-core:v0.2.19 -quay.io/tigera/prometheus-operator:v3.21.0-2.0 -quay.io/tigera/prometheus-config-reloader:v3.21.0-2.0 +quay.io/tigera/pickle-operator:v3.21.0-2.0 +quay.io/tigera/pickle-config-reloader:v3.21.0-2.0 quay.io/tigera/cc-cni-config-scanner:v0.5`, // curl -0 https://installer.calicocloud.io/manifests/v3.21.0-1.0-5/image-list 'v21.2.0': `quay.io/tigera/cnx-apiserver:v3.21.0-1.0 @@ -565,8 +565,8 @@ quay.io/tigera/policy-recommendation:v3.21.0-1.0 quay.io/tigera/egress-gateway:v3.21.0-1.0 quay.io/tigera/l7-collector:v3.21.0-1.0 quay.io/tigera/envoy:v3.21.0-1.0 -quay.io/tigera/prometheus:v3.21.0-1.0 -quay.io/tigera/prometheus-service:v3.21.0-1.0 +quay.io/tigera/pickle:v3.21.0-1.0 +quay.io/tigera/pickle-service:v3.21.0-1.0 quay.io/tigera/alertmanager:v3.21.0-1.0 quay.io/tigera/cnx-queryserver:v3.21.0-1.0 quay.io/tigera/kube-controllers:v3.21.0-1.0 @@ -593,8 +593,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.6 quay.io/tigera/runtime-security-operator:v1.23.0 quay.io/tigera/skimble:v1.23.0 quay.io/tigera/cc-core:v0.2.18 -quay.io/tigera/prometheus-operator:v3.21.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.21.0-1.0 +quay.io/tigera/pickle-operator:v3.21.0-1.0 +quay.io/tigera/pickle-config-reloader:v3.21.0-1.0 quay.io/tigera/cc-cni-config-scanner:v0.4`, // curl -0 https://installer.calicocloud.io/manifests/v3.21.0-1.0-5/image-list 'v21.1.0': `quay.io/tigera/cnx-apiserver:v3.21.0-1.0 @@ -615,8 +615,8 @@ quay.io/tigera/policy-recommendation:v3.21.0-1.0 quay.io/tigera/egress-gateway:v3.21.0-1.0 quay.io/tigera/l7-collector:v3.21.0-1.0 quay.io/tigera/envoy:v3.21.0-1.0 -quay.io/tigera/prometheus:v3.21.0-1.0 -quay.io/tigera/prometheus-service:v3.21.0-1.0 +quay.io/tigera/pickle:v3.21.0-1.0 +quay.io/tigera/pickle-service:v3.21.0-1.0 quay.io/tigera/alertmanager:v3.21.0-1.0 quay.io/tigera/cnx-queryserver:v3.21.0-1.0 quay.io/tigera/kube-controllers:v3.21.0-1.0 @@ -643,8 +643,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.6 quay.io/tigera/runtime-security-operator:v1.23.0 quay.io/tigera/skimble:v1.23.0 quay.io/tigera/cc-core:v0.2.18 -quay.io/tigera/prometheus-operator:v3.21.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.21.0-1.0 +quay.io/tigera/pickle-operator:v3.21.0-1.0 +quay.io/tigera/pickle-config-reloader:v3.21.0-1.0 quay.io/tigera/cc-cni-config-scanner:v0.4`, // curl -0 https://installer.calicocloud.io/manifests/v3.21.0-1.0-4/image-list 'v21.0.0': `quay.io/tigera/cnx-apiserver:v3.21.0-1.0 @@ -665,8 +665,8 @@ quay.io/tigera/policy-recommendation:v3.21.0-1.0 quay.io/tigera/egress-gateway:v3.21.0-1.0 quay.io/tigera/l7-collector:v3.21.0-1.0 quay.io/tigera/envoy:v3.21.0-1.0 -quay.io/tigera/prometheus:v3.21.0-1.0 -quay.io/tigera/prometheus-service:v3.21.0-1.0 +quay.io/tigera/pickle:v3.21.0-1.0 +quay.io/tigera/pickle-service:v3.21.0-1.0 quay.io/tigera/alertmanager:v3.21.0-1.0 quay.io/tigera/cnx-queryserver:v3.21.0-1.0 quay.io/tigera/kube-controllers:v3.21.0-1.0 @@ -693,8 +693,8 @@ quay.io/tigera/image-assurance-cluster-scanner:v1.22.6 quay.io/tigera/runtime-security-operator:v1.23.0 quay.io/tigera/skimble:v1.23.0 quay.io/tigera/cc-core:v0.2.16 -quay.io/tigera/prometheus-operator:v3.21.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.21.0-1.0 +quay.io/tigera/pickle-operator:v3.21.0-1.0 +quay.io/tigera/pickle-config-reloader:v3.21.0-1.0 quay.io/tigera/cc-cni-config-scanner:v0.3`, }; diff --git a/src/utils/linkChecker.js b/src/utils/linkChecker.js index e529d5d596..546cd8d12f 100644 --- a/src/utils/linkChecker.js +++ b/src/utils/linkChecker.js @@ -15,7 +15,7 @@ const defaultSkipList = [ /^https?:\/\/my\.threatfeed\.com/, /^https?:\/\/mycalicocl-calicodemorg-03a087-36558dbb\.hcp\.canadaeast\.azmk8s\.io/, /^https?:\/\/60F939227672BC3D5A1B3EC9744B2B21\.gr7\.us-west-2\.eks\.amazonaws\.com/, - /^https?:\/\/prometheus-dashboard-svc\.calico-monitoring\.svc/, + /^https?:\/\/pickle-dashboard-svc\.calico-monitoring\.svc/, /^https?:\/\/manager\.apps\.demo-ocp\.tigera-solutions\.io/, /^https?:\/\/d881b853ae9313e00302a84f1e346a77\.gr7\.us-west-2\.eks\.amazonaws\.com/, /^https?:\/\/api\.my-ocp-domain\.com/, diff --git a/static/_headers b/static/_headers index 85e004308a..dc01231c9c 100644 --- a/static/_headers +++ b/static/_headers @@ -222,7 +222,7 @@ X-Robots-Tag: noindex /calico-enterprise/latest/operations/monitor X-Robots-Tag: noindex -/calico-enterprise/latest/operations/monitor/prometheus +/calico-enterprise/latest/operations/monitor/pickle X-Robots-Tag: noindex /calico-enterprise/latest/operations/troubleshoot X-Robots-Tag: noindex @@ -384,7 +384,7 @@ X-Robots-Tag: noindex /calico-cloud/operations/monitor X-Robots-Tag: noindex -/calico-cloud/operations/monitor/prometheus +/calico-cloud/operations/monitor/pickle X-Robots-Tag: noindex /calico-cloud/operations X-Robots-Tag: noindex diff --git a/static/_redirects b/static/_redirects index f8618d2960..8b09e94e06 100644 --- a/static/_redirects +++ b/static/_redirects @@ -250,8 +250,8 @@ /maintenance/kubernetes-upgrade-tsee/operator https://docs.tigera.io/calico-enterprise/latest/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator 301 /maintenance/manifest-archive https://docs.tigera.io/calico-enterprise/latest/getting-started/manifest-archive 301 /maintenance/monitor/metrics/metrics https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/ 301 -/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/ 301 -/maintenance/monitor/support https://docs.tigera.io/calico-enterprise/latest/monitor/prometheus/support 301 +/maintenance/monitor/pickle/pickle https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/ 301 +/maintenance/monitor/support https://docs.tigera.io/calico-enterprise/latest/monitor/pickle/support 301 /maintenance/monitor/elasticsearch-and-fluentd-metrics /calico-enterprise/latest/operations/monitor/metrics/elasticsearch-and-fluentd-metrics 301 /maintenance/monitor/license-agent /calico-enterprise/latest/operations/license-options 301 /maintenance/openshift-upgrade https://docs.tigera.io/calico-enterprise/latest/getting-started/upgrading/upgrading-enterprise/openshift-upgrade 301 @@ -292,12 +292,12 @@ /reference/compliance-reports/* https://docs.tigera.io/calico-enterprise/latest/compliance 301 /reference/felix/ https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/ 301 /reference/felix/configuration https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration 301 -/reference/felix/prometheus https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus 301 +/reference/felix/pickle https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle 301 /reference/host-endpoints/donottrack https://docs.tigera.io/calico-enterprise/latest/reference/host-endpoints 301 /reference/host-endpoints/tutorial https://docs.tigera.io/calico-enterprise/latest/reference/host-endpoints 301 /reference/kube-controllers/ https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/ 301 /reference/kube-controllers/configuration https://docs.tigera.io/calico-enterprise/latest/reference/resources/kubecontrollersconfig 301 -/reference/kube-controllers/prometheus https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/prometheus 301 +/reference/kube-controllers/pickle https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/pickle 301 /reference/legal/ https://docs.tigera.io/calico-enterprise/latest/reference/attribution 301 /reference/node/ https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/ 301 /reference/node/configuration https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/configuration 301 diff --git a/static/calico-cloud/llms-full.txt b/static/calico-cloud/llms-full.txt index 90a57ccebd..c6780ff5a5 100644 --- a/static/calico-cloud/llms-full.txt +++ b/static/calico-cloud/llms-full.txt @@ -1797,9 +1797,9 @@ quay.io/tigera/gateway-l7-collector:v3.23.1 quay.io/tigera/envoy:v3.23.1 -quay.io/tigera/prometheus:v3.23.1 +quay.io/tigera/pickle:v3.23.1 -quay.io/tigera/prometheus-service:v3.23.1 +quay.io/tigera/pickle-service:v3.23.1 quay.io/tigera/alertmanager:v3.23.1 @@ -1851,9 +1851,9 @@ quay.io/tigera/operator:v1.42.4 quay.io/tigera/cc-core:v0.3.8 -quay.io/tigera/prometheus-operator:v3.23.1 +quay.io/tigera/pickle-operator:v3.23.1 -quay.io/tigera/prometheus-config-reloader:v3.23.1 +quay.io/tigera/pickle-config-reloader:v3.23.1 quay.io/tigera/cc-cni-config-scanner:v0.7.3 @@ -3009,10 +3009,10 @@ cmEtdm9sdHJvbjAeFw0yMDEyMjExOTA1MzhaFw0yNTEyMjAxOTA1MzhaMBkxFzAV **8 - monitor** -`monitor` is responsible for configuring prometheus and associated custom resources. Check the pods and logs in the `tigera-prometheus` namespace. +`monitor` is responsible for configuring pickle and associated custom resources. Check the pods and logs in the `tigera-pickle` namespace. ```bash -$ kubectl get pods -n tigera-prometheus +$ kubectl get pods -n tigera-pickle ``` ```text @@ -3024,9 +3024,9 @@ alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ### Check additional custom resources[​](#check-additional-custom-resources) @@ -3072,7 +3072,7 @@ default 120m The installation script deploys a Prometheus operator and associated custom resources. If you already have a Prometheus operator running in your cluster, contact Tigera support. ```bash -kubectl get pods -n tigera-prometheus +kubectl get pods -n tigera-pickle ``` ```text @@ -3084,9 +3084,9 @@ alertmanager-calico-node-alertmanager-1 2/2 Running 0 125m alertmanager-calico-node-alertmanager-2 2/2 Running 0 125m -calico-prometheus-operator-77bf897c9b-7f88x 1/1 Running 0 125m +calico-pickle-operator-77bf897c9b-7f88x 1/1 Running 0 125m -prometheus-calico-node-prometheus-0 3/3 Running 1 125m +pickle-calico-node-pickle-0 3/3 Running 1 125m ``` ## Check pod capacity[​](#check-pod-capacity) @@ -3096,7 +3096,7 @@ If cluster does not have enough capacity, it will not be able to deploy pods. Th The high-level components Calico Cloud needs to run are: - Per node: 1 fluentd, 1 compliance benchmarker -- On top of per node: 3 alertmanager (from statefulset), 1 prometheus, 1 prometheus operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver +- On top of per node: 3 alertmanager (from statefulset), 1 pickle, 1 pickle operator, 1 kube-controllers, 2 compliance snapshotter and controller, 1 guardian, 1 ids controller, 1 apiserver Some clusters have limited pod-networked pod capacity. @@ -10702,23 +10702,23 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ```text Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -10733,7 +10733,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace For each workload endpoint, the `Policies:` section lists the policies that apply to that endpoint, in the order they apply. calicoq displays both Calico Cloud Policies and Kubernetes NetworkPolicies, although this example focuses on the latter. The `Rule matches:` section lists the policies that match that endpoint in their rules, in other words that have rules that deny or allow that endpoint as a packet source or destination. - Focusing on the `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + Focusing on the `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to the Calico Cloud format (note the addition of the namespace test). @@ -17176,7 +17176,7 @@ Your target application must be configured to receive data from the Calico Cloud - ``: the name of your Alertmanager service. - ``: the namespace associated with your Alertmanager service. If no namespace is specified in the Alertmanager service resource, then this value is `default`. - Alertmanager integration in Calico Cloud leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + Alertmanager integration in Calico Cloud leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). - **Generic JSON.** You must have a webhook URL for any other application you want the Calico Cloud webhook to send alerts to. @@ -24666,7 +24666,7 @@ In Calico Cloud, we program these LUTs to the eBPF data plane as maps which can ## Additional resources[​](#additional-resources) -- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus#load-balancer-metrics) +- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle#load-balancer-metrics) - [FelixConfiguration](https://docs.tigera.io/calico-cloud/reference/resources/felixconfig) - [Enable the eBPF data plane](https://docs.tigera.io/calico-cloud/operations/ebpf/enabling-ebpf) - [Advertise Service IPs with BGP](https://docs.tigera.io/calico-cloud/networking/configuring/advertise-service-ips) @@ -24715,7 +24715,7 @@ It is not possible to remove all backends of a service from backend selection vi - [Enable the eBPF data plane](https://docs.tigera.io/calico-cloud/operations/ebpf/enabling-ebpf) - [Maglev Load Balancing](https://docs.tigera.io/calico-cloud/networking/configuring/add-maglev-load-balancing) -- [Prometheus Metrics](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus#load-balancer-metrics) +- [Prometheus Metrics](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle#load-balancer-metrics) ### Egress gateways @@ -31084,25 +31084,25 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring[​](#monitoring) -##### [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) +##### [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) -[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) +[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) ##### [Recommended Prometheus metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) [Recommended Prometheus metrics for Calico Cloud Typha, Felix, and policy components on connected clusters, covering the signals most critical to cluster health.](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) -##### [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) +##### [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) -[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) +[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) -##### [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) +##### [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) -[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) +[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) -##### [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) +##### [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) -[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) +[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) ##### [BGP metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/bgp-metrics) @@ -31211,7 +31211,7 @@ The script migrates all applicable Calico Cloud components to open-source Projec 3. Run the script and read the help to determine if you need to specify any flags `./downgrade.sh --help`. -4. Run the script with any needed flags, for example: `./downgrade.sh --remove-prometheus`. +4. Run the script with any needed flags, for example: `./downgrade.sh --remove-pickle`. ## Next steps[​](#next-steps) @@ -31357,14 +31357,14 @@ The **Deployed to** column shows the namespace where the operator places the sec | ------------------------------------- | ----------------------------------- | ---------------------- | -------------------------------- | | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `node-certs` | `typha-client` | `calico-system` | Installation/default | | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | | `typha-certs` | `typha-server` | `calico-system` | Installation/default | | `typha-certs-noncluster-host` | `typha-server-noncluster-host` | `calico-system` | Installation/default | @@ -31474,9 +31474,9 @@ CSR names follow the pattern: `::`. -## [🗃Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) +## [🗃Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) -[5 items](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) +[5 items](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) ## [🗃Metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/) @@ -31486,31 +31486,31 @@ CSR names follow the pattern: `::`. -## [📄️Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) +## [📄️Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) -[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) +[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) ## [📄️Recommended Prometheus metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) [Recommended Prometheus metrics for Calico Cloud Typha, Felix, and policy components on connected clusters, covering the signals most critical to cluster health.](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) -## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) +## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) -[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) +[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) -## [📄️Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) +## [📄️Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) -[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) +[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) -## [📄️Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) +## [📄️Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) -[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) +[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) ### Prometheus support ## Big picture[​](#big-picture) -Calico Cloud uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Cloud components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +Calico Cloud uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Cloud components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options[​](#install-options) @@ -31518,9 +31518,9 @@ Calico Cloud uses the open-source [Prometheus monitoring and alerting toolkit](h You install the Calico Cloud Prometheus operator and CRDs during Calico Cloud installation. Calico Cloud metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. - If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because Calico Cloud creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. + If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because Calico Cloud creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) +- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) ### Recommended Prometheus metrics @@ -32106,13 +32106,13 @@ Calico Cloud uses the Prometheus monitoring tool to scrape metrics from instrume **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](https://docs.tigera.io/calico-cloud/release-notes/) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](https://docs.tigera.io/calico-cloud/release-notes/) (`coreos-pickle`). ## How to[​](#how-to) - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -32120,7 +32120,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -32137,13 +32137,13 @@ The following example shows a Prometheus server installed in namespace "external externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](https://docs.tigera.io/calico-cloud/reference/installation/api). @@ -32157,20 +32157,20 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus + export NS=external-pickle - kubectl get servicemonitor -n $NS tigera-external-prometheus + kubectl get servicemonitor -n $NS tigera-external-pickle - kubectl get serviceaccount -n $NS tigera-external-prometheus + kubectl get serviceaccount -n $NS tigera-external-pickle - kubectl get secret -n $NS tigera-external-prometheus + kubectl get secret -n $NS tigera-external-pickle - kubectl get clusterrole tigera-external-prometheus + kubectl get clusterrole tigera-external-pickle - kubectl get clusterrolebinding tigera-external-prometheus + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly[​](#scrape-metrics-from-specific-components-directly) @@ -32187,19 +32187,19 @@ We recommend the previous section for scraping all enabled metrics. Read on if y 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -32211,11 +32211,11 @@ We recommend the previous section for scraping all enabled metrics. Read on if y Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32229,19 +32229,19 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -32253,11 +32253,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32271,19 +32271,19 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -32295,11 +32295,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -32313,19 +32313,19 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -32337,11 +32337,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32357,7 +32357,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -32368,7 +32368,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration). -For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus). +For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle). **For Windows nodes, create a service to expose Felix metrics** @@ -32421,11 +32421,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32455,23 +32455,23 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. -### Verify BYO Prometheus[​](#verify-byo-prometheus) +### Verify BYO Prometheus[​](#verify-byo-pickle) 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 2. Browse to the Prometheus dashboard: [http://localhost:9090](http://localhost:9090). @@ -32487,11 +32487,11 @@ This section is applicable only if you experience issues with mTLS after followi 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 2. Port-forward the Prometheus pods and run this command with the forwarded port. @@ -32515,16 +32515,16 @@ This is an example of how to modify the sample rule created by the sample manife - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -32537,13 +32537,13 @@ metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -32579,13 +32579,13 @@ metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -32612,11 +32612,11 @@ spec: ## Creating a new alerting rule[​](#creating-a-new-alerting-rule) -Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) and [Queries](https://prometheus.io/docs/querying/examples/) for more information. +Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node[​](#new-alerting-rule-for-monitoring-calico-node) -To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest in the `tigera-prometheus` namespace with the labels `role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. +To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest in the `tigera-pickle` namespace with the labels `role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire a alert when a calico-node instance has been down for more than 5 minutes, save the following to a file, say `calico-node-down-alert.yaml`. @@ -32627,15 +32627,15 @@ kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down + name: calico-pickle-calico-node-down - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -32668,11 +32668,11 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). ### New alerting rule for monitoring BGP peers[​](#new-alerting-rule-for-monitoring-bgp-peers) -Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels `role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. +Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels `role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” is increasing at a non-zero rate in the cluster (over the last 5 minutes), save the following to a file, say `tigera-peer-status-not-established.yaml`. @@ -32685,13 +32685,13 @@ metadata: labels: - prometheus: calico-node-prometheus + pickle: calico-node-pickle - role: tigera-prometheus-rules + role: tigera-pickle-rules - name: tigera-prometheus-peer-status-not-established + name: tigera-pickle-peer-status-not-established - namespace: tigera-prometheus + namespace: tigera-pickle spec: @@ -32726,7 +32726,7 @@ Then create/apply this manifest in kubernetes. kubectl apply -f tigera-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). ## Additional Alerting Rules[​](#additional-alerting-rules) @@ -32819,7 +32819,7 @@ The scrape interval of endpoints (calico-node in our case) is defined as part of - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and apply the updated manifest. @@ -32828,7 +32828,7 @@ The scrape interval of endpoints (calico-node in our case) is defined as part of kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -32841,7 +32841,7 @@ metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: @@ -32879,7 +32879,7 @@ metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: @@ -32910,16 +32910,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from ConfigMap's or Secret's and will perform steps necessary for reloading the configuration. @@ -32928,7 +32928,7 @@ The config-reloaders watch each pods file-system for updated config from ConfigM Alertmanager is used by Calico Cloud to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config[​](#updating-the-alertmanager-config) @@ -32956,9 +32956,9 @@ More detailed information about Alertmanager is available in the [upstream docum kubectl -n tigera-operator apply -f alertmanager-secret.yaml ``` -Your changes should be applied in a few seconds by the config-reloader container inside the alertmanager pod launched by the prometheus-operator (usually named `alertmanager-`). +Your changes should be applied in a few seconds by the config-reloader container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). -For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules[​](#configure-inhibition-rules) @@ -33016,7 +33016,7 @@ receivers: - url: 'http://calico-alertmanager-webhook:30501/' ``` -More information, including descriptions of the various options can be found under the [route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. +More information, including descriptions of the various options can be found under the [route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. ### Metrics @@ -33090,7 +33090,7 @@ BGP metric reporting is accomplished using three key pieces: - Prometheus Server - Prometheus Alertmanager -### About Prometheus[​](#about-prometheus) +### About Prometheus[​](#about-pickle) The Prometheus scrapes various instrumented jobs (endpoints) to collect time series data for a given set of metrics. Time series data can then be queried and rules can be setup to monitor specific thresholds to trigger alerts. The data can also be visualized (such as using Grafana). @@ -33125,11 +33125,11 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 2. Verify you can access the metrics. @@ -33138,7 +33138,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric[​](#bgp-peers-metric) @@ -33204,7 +33204,7 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources[​](#additional-resources) -- [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) +- [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) ### Policy metrics @@ -33277,7 +33277,7 @@ Policy inspection and reporting is accomplished using four key pieces: Metrics will only be generated at a node when there are packets directed at an endpoint that are being actively profiled by a policy. Once generated they stay alive for 60 seconds. -Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) for more information. +Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) for more information. Because of metrics being expired, as just described, it is entirely possible for a GET on a metrics query URL to return no information. This is expected if there have not been any packets being processed by a policy on that node, in the last 60 seconds. @@ -33356,7 +33356,7 @@ Platform engineering teams rely on logs for visibility into their networks. If c ## How to[​](#how-to) -### Create Prometheus alerts for Fluentd[​](#create-prometheus-alerts-for-fluentd) +### Create Prometheus alerts for Fluentd[​](#create-pickle-alerts-for-fluentd) The following example creates a Prometheus rule to monitor some important Fluentd metrics, and alert when they have crossed certain thresholds: @@ -33367,15 +33367,15 @@ kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring + name: tigera-pickle-log-collection-monitoring - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -34563,9 +34563,9 @@ APIs, CLI, architecture and design, and FAQ. [Reference for setting Kubernetes resource requests and limits on Calico Cloud components managed by the Tigera Operator in connected clusters.](https://docs.tigera.io/calico-cloud/reference/component-resources/configure-resources) -##### [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus) +##### [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle) -[Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth.](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus) +[Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth.](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle) ##### [Configuring cnx-node](https://docs.tigera.io/calico-cloud/reference/component-resources/node/configuration) @@ -34575,9 +34575,9 @@ APIs, CLI, architecture and design, and FAQ. [Reference for Felix configuration parameters in Calico Cloud connected clusters covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration) -##### [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) +##### [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) -[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) +[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) ## Configuration on public clouds[​](#configuration-on-public-clouds) @@ -35403,7 +35403,7 @@ CalicoNodeDaemonSetInitContainer is a calico-node DaemonSet init container. | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `name` *string* | Name is an enum which identifies the calico-node DaemonSet init container by name. Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` *string* | Name is an enum which identifies the calico-node DaemonSet init container by name. Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | ### CalicoNodeDaemonSetPodSpec[​](#caliconodedaemonsetpodspec) @@ -35486,7 +35486,7 @@ CalicoNodeWindowsDaemonSetInitContainer is a calico-node-windows DaemonSet init | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `name` *string* | Name is an enum which identifies the calico-node-windows DaemonSet init container by name. Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` *string* | Name is an enum which identifies the calico-node-windows DaemonSet init container by name. Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | ### CalicoNodeWindowsDaemonSetPodSpec[​](#caliconodewindowsdaemonsetpodspec) @@ -35626,15 +35626,15 @@ CertificateManagement configures pods to submit a CertificateSigningRequest to t | `Enabled` | | | `Disabled` | | -### CommonPrometheusFields[​](#commonprometheusfields) +### CommonPrometheusFields[​](#commonpicklefields) *Appears in:* -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `containers` *[PrometheusContainer](#prometheuscontainer) array* | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` *[PrometheusContainer](#picklecontainer) array* | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | Define resources requests and limits for single Pods. | ### Compliance[​](#compliance) @@ -36833,7 +36833,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | `honorLabels` *boolean* | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` *boolean* | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` *RelabelConfig array* | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: [https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel\_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) | +| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: [https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel\_config](https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config) | ### EnvoySettings[​](#envoysettings) @@ -36846,7 +36846,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | `xffNumTrustedHops` *integer* | (Optional) The number of additional ingress proxy hops from the right side of the x-forwarded-for HTTP header to trust when determining the origin client’s IP address. 0 is permitted, but >=1 is the typical setting. | | `useRemoteAddress` *boolean* | (Optional) If set to true, the Envoy connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. | -### ExternalPrometheus[​](#externalprometheus) +### ExternalPrometheus[​](#externalpickle) *Appears in:* @@ -36854,7 +36854,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | Field | Description | | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `serviceMonitor` *[ServiceMonitor](#servicemonitor)* | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` *[ServiceMonitor](#servicemonitor)* | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` *string* | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | ### FIPSMode[​](#fipsmode) @@ -36905,7 +36905,7 @@ FluentdDaemonSetInitContainer is a Fluentd DaemonSet init container. | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `name` *string* | Name is an enum which identifies the Fluentd DaemonSet init container by name. Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` *string* | Name is an enum which identifies the Fluentd DaemonSet init container by name. Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | ### FluentdDaemonSetPodSpec[​](#fluentddaemonsetpodspec) @@ -37739,8 +37739,8 @@ InstallationSpec defines configuration for a Calico or Calico Enterprise install | `controlPlaneNodeSelector` *object (keys:string, values:string)* | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array* | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` *integer* | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` *integer* | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` *integer* | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` *integer* | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` *integer* | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` *string* | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` *string* | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled. Default: /var/lib/kubelet | | `nodeUpdateStrategy` *[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)* | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -38638,8 +38638,8 @@ MonitorSpec defines the desired state of Tigera monitor. | Field | Description | | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `externalPrometheus` *[ExternalPrometheus](#externalprometheus)* | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` *[Prometheus](#prometheus)* | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` *[ExternalPrometheus](#externalpickle)* | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` *[Prometheus](#pickle)* | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` *[AlertManager](#alertmanager)* | (Optional) AlertManager is the configuration for the AlertManager. | ### MonitorStatus[​](#monitorstatus) @@ -39122,7 +39122,7 @@ One of: Calico, CalicoEnterprise - [InstallationSpec](#installationspec) - [InstallationStatus](#installationstatus) -### Prometheus[​](#prometheus) +### Prometheus[​](#pickle) *Appears in:* @@ -39130,30 +39130,30 @@ One of: Calico, CalicoEnterprise | Field | Description | | ------------------------------------------ | ------------------------------------------------------- | -| `spec` *[PrometheusSpec](#prometheusspec)* | (Optional) Spec is the specification of the Prometheus. | +| `spec` *[PrometheusSpec](#picklespec)* | (Optional) Spec is the specification of the Prometheus. | -### PrometheusContainer[​](#prometheuscontainer) +### PrometheusContainer[​](#picklecontainer) PrometheusContainer is a Prometheus container. *Appears in:* -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` *string* | Name is an enum which identifies the Prometheus Deployment container by name. Supported values are: authn-proxy | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Prometheus container's resources. If omitted, the Prometheus will use its default value for this container's resources. | -### PrometheusSpec[​](#prometheusspec) +### PrometheusSpec[​](#picklespec) *Appears in:* -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -| `commonPrometheusFields` *[CommonPrometheusFields](#commonprometheusfields)* | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` *[CommonPrometheusFields](#commonpicklefields)* | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType[​](#prompttype) @@ -39254,12 +39254,12 @@ S3StoreSpec defines configuration for exporting logs to Amazon S3. *Appears in:* -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up. Default: k8s-app=tigera-prometheus | -| `endpoints` *[Endpoint](#endpoint) array* | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` *object (keys:string, values:string)* | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up. Default: k8s-app=tigera-pickle | +| `endpoints` *[Endpoint](#endpoint) array* | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType[​](#sidecarstatustype) @@ -41834,94 +41834,94 @@ spec: | Schema | One of: `Debug`, `Error`, `Fatal`, `Info`, `Trace`, `Warning`. | | Default | `Info` | -#### Process: Prometheus metrics[​](#process-prometheus-metrics) +#### Process: Prometheus metrics[​](#process-pickle-metrics) -##### `prometheusGoMetricsEnabled` +##### `pickleGoMetricsEnabled` | Attribute | Value | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Key | `prometheusGoMetricsEnabled` | +| Key | `pickleGoMetricsEnabled` | | Description | Disables Go runtime metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | -##### `prometheusMetricsCAFile` +##### `pickleMetricsCAFile` | Attribute | Value | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsCAFile` | +| Key | `pickleMetricsCAFile` | | Description | Defines the absolute path to the TLS CA certificate file used for securing the /metrics endpoint. This certificate must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsCertFile` +##### `pickleMetricsCertFile` | Attribute | Value | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Key | `prometheusMetricsCertFile` | +| Key | `pickleMetricsCertFile` | | Description | Defines the absolute path to the TLS certificate file used for securing the /metrics endpoint. This certificate must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsClientAuth` +##### `pickleMetricsClientAuth` | Attribute | Value | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsClientAuth` | +| Key | `pickleMetricsClientAuth` | | Description | Specifies the client authentication type for the /metrics endpoint. This determines how the server validates client certificates. Default is "RequireAndVerifyClientCert". | | Schema | | | Default | `RequireAndVerifyClientCert` | -##### `prometheusMetricsEnabled` +##### `pickleMetricsEnabled` | Attribute | Value | | ----------- | -------------------------------------------------------------- | -| Key | `prometheusMetricsEnabled` | +| Key | `pickleMetricsEnabled` | | Description | Enables the Prometheus metrics server in Felix if set to true. | | Schema | Boolean. | | Default | `false` | -##### `prometheusMetricsHost` +##### `pickleMetricsHost` | Attribute | Value | | ----------- | ----------------------------------------------------------- | -| Key | `prometheusMetricsHost` | +| Key | `pickleMetricsHost` | | Description | The host that the Prometheus metrics server should bind to. | | Schema | String. | | Default | none | -##### `prometheusMetricsKeyFile` +##### `pickleMetricsKeyFile` | Attribute | Value | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsKeyFile` | +| Key | `pickleMetricsKeyFile` | | Description | Defines the absolute path to the private key file corresponding to the TLS certificate used for securing the /metrics endpoint. The private key must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsPort` +##### `pickleMetricsPort` | Attribute | Value | | ----------- | --------------------------------------------------------------- | -| Key | `prometheusMetricsPort` | +| Key | `pickleMetricsPort` | | Description | The TCP port that the Prometheus metrics server should bind to. | | Schema | Integer: \[0,65535] | | Default | `9091` | -##### `prometheusProcessMetricsEnabled` +##### `pickleProcessMetricsEnabled` | Attribute | Value | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusProcessMetricsEnabled` | +| Key | `pickleProcessMetricsEnabled` | | Description | Disables process metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | -##### `prometheusWireGuardMetricsEnabled` +##### `pickleWireGuardMetricsEnabled` | Attribute | Value | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusWireGuardMetricsEnabled` | +| Key | `pickleWireGuardMetricsEnabled` | | Description | Disables wireguard metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | @@ -43442,7 +43442,7 @@ spec: | Schema | Duration string, for example `1m30s123ms` or `1h5m`. | | Default | `10m0s` | -#### Flow logs: Prometheus reports[​](#flow-logs-prometheus-reports) +#### Flow logs: Prometheus reports[​](#flow-logs-pickle-reports) ##### `deletedMetricsRetentionSecs` @@ -43453,47 +43453,47 @@ spec: | Schema | Integer. | | Default | `30s` | -##### `prometheusReporterCAFile` +##### `pickleReporterCAFile` | Attribute | Value | | ----------- | ------------------------------------------------------------------------- | -| Key | `prometheusReporterCAFile` | +| Key | `pickleReporterCAFile` | | Description | The path to the TLS CA file for the Prometheus per-flow metrics reporter. | | Schema | String. | | Default | none | -##### `prometheusReporterCertFile` +##### `pickleReporterCertFile` | Attribute | Value | | ----------- | ---------------------------------------------------------------------------------- | -| Key | `prometheusReporterCertFile` | +| Key | `pickleReporterCertFile` | | Description | The path to the TLS certificate file for the Prometheus per-flow metrics reporter. | | Schema | String. | | Default | none | -##### `prometheusReporterEnabled` +##### `pickleReporterEnabled` | Attribute | Value | | ----------- | ---------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusReporterEnabled` | +| Key | `pickleReporterEnabled` | | Description | Controls whether the Prometheus per-flow metrics reporter is enabled. This is used to show real-time flow metrics in the UI. | | Schema | Boolean. | | Default | `false` | -##### `prometheusReporterKeyFile` +##### `pickleReporterKeyFile` | Attribute | Value | | ----------- | ---------------------------------------------------------------------------------- | -| Key | `prometheusReporterKeyFile` | +| Key | `pickleReporterKeyFile` | | Description | The path to the TLS private key file for the Prometheus per-flow metrics reporter. | | Schema | String. | | Default | none | -##### `prometheusReporterPort` +##### `pickleReporterPort` | Attribute | Value | | ----------- | ---------------------------------------------------------------------- | -| Key | `prometheusReporterPort` | +| Key | `pickleReporterPort` | | Description | The port that the Prometheus per-flow metrics reporter should bind to. | | Schema | Integer: \[0,65535] | | Default | `9092` | @@ -46458,7 +46458,7 @@ spec: healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: @@ -46519,7 +46519,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers[​](#controllers) @@ -50818,7 +50818,7 @@ This command will output the configured resource requests and limits for the Pac The `tigera/kube-controllers` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the Calico Cloud datastore. - To configure the controllers, see the [KubeControllersConfiguration](https://docs.tigera.io/calico-cloud/reference/resources/kubecontrollersconfig) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus). +- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle). ### Monitoring kube-controllers with Prometheus @@ -51181,9 +51181,9 @@ Setting CALICO\_ROUTER\_ID to value `hash` will use a hash of the configured nod [Reference for Felix configuration parameters in Calico Cloud connected clusters covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration) -## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) +## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) -[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) +[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) ### Configuring Felix @@ -52080,7 +52080,7 @@ The full list of parameters which can be set is as follows. -### Process: Prometheus metrics[​](#process-prometheus-metrics) +### Process: Prometheus metrics[​](#process-pickle-metrics) #### `PrometheusGoMetricsEnabled` @@ -56376,7 +56376,7 @@ The full list of parameters which can be set is as follows. -### Flow logs: Prometheus reports[​](#flow-logs-prometheus-reports) +### Flow logs: Prometheus reports[​](#flow-logs-pickle-reports) #### `DeletedMetricsRetentionSecs` @@ -60434,7 +60434,7 @@ Calico Cloud incorporates various open source software. The following open sourc | github.com/projectcalico/libcalico-go | github.com/projectcalico/libcalico-go/lib | Apache 2.0 | | github.com/projectcalico/pod2daemon | github.com/projectcalico/pod2daemon | Apache 2.0 | | typha | typha | Tigera Proprietary | -| github.com/prometheus/client\_golang/ | github.com/prometheus/client\_golang/prometheus-v1.7.1 | Apache 2.0 | +| github.com/pickle/client\_golang/ | github.com/pickle/client\_golang/pickle-v1.7.1 | Apache 2.0 | | github.com/rakelkar/gonetsh/netsh | github.com/rakelkar/gonetsh/netsh-e5c5ffe4bdf04bc060fc45ff4aca2349f51c94a7 | Apache 2.0 | | github.com/robfig/cron | github.com/robfig/cron-v1.2.0 | MIT | | github.com/satori/go.uuid | github.com/satori/go.uuid-v1.2.0 | MIT | diff --git a/static/calico-cloud/llms.txt b/static/calico-cloud/llms.txt index 32467aadc7..f71f44933f 100644 --- a/static/calico-cloud/llms.txt +++ b/static/calico-cloud/llms.txt @@ -227,12 +227,12 @@ - [Access usage data programmatically](https://docs.tigera.io/calico-cloud/operations/usage-api): Create a read-only API key in the Calico Cloud web console and use it to call the Usage API to retrieve vCPU usage data programmatically. - [Provide TLS certificates for Calico components](https://docs.tigera.io/calico-cloud/operations/comms/): Provide custom TLS certificates for Calico components. - [Monitoring](https://docs.tigera.io/calico-cloud/operations/monitor/): Reference index for monitoring Calico Cloud connected clusters with Prometheus metrics covering BGP, policy, log collection, and component health. -- [Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Cloud for component metrics, alerts, and persistent storage on connected clusters. -- [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support): Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options. +- [Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Cloud for component metrics, alerts, and persistent storage on connected clusters. +- [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support): Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options. - [Recommended Prometheus metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics): Recommended Prometheus metrics for Calico Cloud Typha, Felix, and policy components on connected clusters, covering the signals most critical to cluster health. -- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus): Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters. -- [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus): Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources. -- [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager): Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. +- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle): Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters. +- [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle): Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources. +- [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager): Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. - [Metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/): Reference index for Calico Cloud Prometheus metrics on connected clusters covering BGP, policy, log collection, and recommended dashboards. - [BGP metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/bgp-metrics): Monitor BGP peering and route exchange in Calico Cloud connected clusters by defining Prometheus rules and thresholds for peer health and route counts. - [Policy metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/policy-metrics): Monitor the runtime effect of policies on Calico Cloud connected clusters by defining Prometheus rules and thresholds that fire alerts on policy hits. @@ -297,12 +297,12 @@ - [Configuring the Calico Cloud CNI plugins](https://docs.tigera.io/calico-cloud/reference/component-resources/configuration): Reference for configuring the CNI plugin in Calico Cloud connected clusters covering operator-managed and manifest-mode CNI options. - [Configure resource requests and limits](https://docs.tigera.io/calico-cloud/reference/component-resources/configure-resources): Reference for setting Kubernetes resource requests and limits on Calico Cloud components managed by the Tigera Operator in connected clusters. - [kube-controllers](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/): kube-controllers is a set of Kubernetes controllers for Calico Cloud. -- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus): Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth. +- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle): Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth. - [Calico Cloud node (cnx-node)](https://docs.tigera.io/calico-cloud/reference/component-resources/node/): Reference content for the cnx-node component in Calico Cloud connected clusters covering Felix, BIRD, and the per-node agent configuration. - [Configuring cnx-node](https://docs.tigera.io/calico-cloud/reference/component-resources/node/configuration): Reference for configuring the cnx-node container in Calico Cloud connected clusters through environment variables that control Felix, BIRD, and confd. - [Felix](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/): Reference content for Felix in Calico Cloud connected clusters, the per-node daemon that programs routes and tiered policy rules into the Linux data plane. - [Configuring Felix](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration): Reference for Felix configuration parameters in Calico Cloud connected clusters covering environment variables, FelixConfiguration fields, and per-node overrides. -- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus): Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation. +- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle): Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation. - [Configuration on public clouds](https://docs.tigera.io/calico-cloud/reference/public-cloud/): Public cloud reference for Calico Cloud covering platform-specific networking notes for AWS, Azure, and GCE connected clusters. - [Amazon Web Services](https://docs.tigera.io/calico-cloud/reference/public-cloud/aws): Reference for connecting Calico Cloud clusters running on Amazon Web Services covering supported networking modes and AWS platform notes. - [Azure](https://docs.tigera.io/calico-cloud/reference/public-cloud/azure): Reference for connecting Calico Cloud clusters running on Microsoft Azure covering supported networking modes and Azure platform notes. diff --git a/static/calico-enterprise/llms-full.txt b/static/calico-enterprise/llms-full.txt index 15b8710fb5..37062e0d9a 100644 --- a/static/calico-enterprise/llms-full.txt +++ b/static/calico-enterprise/llms-full.txt @@ -892,7 +892,7 @@ A Linux host that meets the following requirements. > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. Install your pull secret. @@ -1173,7 +1173,7 @@ The geeky details of what you get: > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -1351,7 +1351,7 @@ To install a standard Calico Enterprise cluster with Helm: ```bash helm install calico-enterprise tigera-operator-v3.23.1-0.tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ @@ -1365,7 +1365,7 @@ To install a standard Calico Enterprise cluster with Helm: ```bash helm install calico-enterprise tigera-operator-v3.23.1-0.tgz -f values.yaml \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ @@ -1794,12 +1794,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml ``` You can now monitor progress with the following command: @@ -2058,12 +2058,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml ``` You can now monitor progress with the following command: @@ -2281,12 +2281,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml ``` You can now monitor progress with the following command: @@ -2421,7 +2421,7 @@ Install Calico Enterprise on an AKS managed Kubernetes cluster. > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -2481,7 +2481,7 @@ Wait until the `apiserver` shows a status of `Available`, then proceed to > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. Install your pull secret. @@ -2831,7 +2831,7 @@ The geeky details of what you get: > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -3118,7 +3118,7 @@ The geeky details of what you get: > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 5. Install your pull secret. @@ -3421,7 +3421,7 @@ The geeky details of what you get: > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. Install your pull secret. @@ -3544,7 +3544,7 @@ The geeky details of what you get: > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. Install your pull secret. @@ -3821,7 +3821,7 @@ The geeky details of what you get: > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -5186,7 +5186,7 @@ To create a Charmed Kubernetes cluster without a CNI, you can customize your dep > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -7448,11 +7448,11 @@ In order to install images from your private registry, you must first pull the i docker pull quay.io/tigera/policy-recommendation:v3.23.1 - docker pull quay.io/tigera/prometheus:v3.23.1 + docker pull quay.io/tigera/pickle:v3.23.1 - docker pull quay.io/tigera/prometheus-config-reloader:v3.23.1 + docker pull quay.io/tigera/pickle-config-reloader:v3.23.1 - docker pull quay.io/tigera/prometheus-operator:v3.23.1 + docker pull quay.io/tigera/pickle-operator:v3.23.1 docker pull quay.io/tigera/queryserver:v3.23.1 @@ -7460,7 +7460,7 @@ In order to install images from your private registry, you must first pull the i docker pull quay.io/tigera/cni:v3.23.1 - docker pull quay.io/tigera/prometheus-service:v3.23.1 + docker pull quay.io/tigera/pickle-service:v3.23.1 docker pull quay.io/tigera/typha:v3.23.1 @@ -7572,11 +7572,11 @@ In order to install images from your private registry, you must first pull the i docker tag quay.io/tigera/policy-recommendation:v3.23.1 $PRIVATE_REGISTRY/tigera/policy-recommendation:v3.23.1 - docker tag quay.io/tigera/prometheus:v3.23.1 $PRIVATE_REGISTRY/tigera/prometheus:v3.23.1 + docker tag quay.io/tigera/pickle:v3.23.1 $PRIVATE_REGISTRY/tigera/pickle:v3.23.1 - docker tag quay.io/tigera/prometheus-config-reloader:v3.23.1 $PRIVATE_REGISTRY/tigera/prometheus-config-reloader:v3.23.1 + docker tag quay.io/tigera/pickle-config-reloader:v3.23.1 $PRIVATE_REGISTRY/tigera/pickle-config-reloader:v3.23.1 - docker tag quay.io/tigera/prometheus-operator:v3.23.1 $PRIVATE_REGISTRY/tigera/prometheus-operator:v3.23.1 + docker tag quay.io/tigera/pickle-operator:v3.23.1 $PRIVATE_REGISTRY/tigera/pickle-operator:v3.23.1 docker tag quay.io/tigera/queryserver:v3.23.1 $PRIVATE_REGISTRY/tigera/queryserver:v3.23.1 @@ -7584,7 +7584,7 @@ In order to install images from your private registry, you must first pull the i docker tag quay.io/tigera/cni:v3.23.1 $PRIVATE_REGISTRY/tigera/cni:v3.23.1 - docker tag quay.io/tigera/prometheus-service:v3.23.1 $PRIVATE_REGISTRY/tigera/prometheus-service:v3.23.1 + docker tag quay.io/tigera/pickle-service:v3.23.1 $PRIVATE_REGISTRY/tigera/pickle-service:v3.23.1 docker tag quay.io/tigera/typha:v3.23.1 $PRIVATE_REGISTRY/tigera/typha:v3.23.1 @@ -7696,11 +7696,11 @@ In order to install images from your private registry, you must first pull the i docker push $PRIVATE_REGISTRY/tigera/policy-recommendation:v3.23.1 - docker push $PRIVATE_REGISTRY/tigera/prometheus:v3.23.1 + docker push $PRIVATE_REGISTRY/tigera/pickle:v3.23.1 - docker push $PRIVATE_REGISTRY/tigera/prometheus-config-reloader:v3.23.1 + docker push $PRIVATE_REGISTRY/tigera/pickle-config-reloader:v3.23.1 - docker push $PRIVATE_REGISTRY/tigera/prometheus-operator:v3.23.1 + docker push $PRIVATE_REGISTRY/tigera/pickle-operator:v3.23.1 docker push $PRIVATE_REGISTRY/tigera/queryserver:v3.23.1 @@ -7708,7 +7708,7 @@ In order to install images from your private registry, you must first pull the i docker push $PRIVATE_REGISTRY/tigera/cni:v3.23.1 - docker push $PRIVATE_REGISTRY/tigera/prometheus-service:v3.23.1 + docker push $PRIVATE_REGISTRY/tigera/pickle-service:v3.23.1 docker push $PRIVATE_REGISTRY/tigera/typha:v3.23.1 @@ -7777,12 +7777,12 @@ Next, ensure that an image pull secret has been configured for your custom regis sed -ie "/serviceAccountName: tigera-operator/a imagePullSecrets:\n - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-operator.yaml ``` -If you are installing Prometheus operator as part of Calico Enterprise, then before applying `tigera-prometheus-operator.yaml`, modify registry references to use your custom registry: +If you are installing Prometheus operator as part of Calico Enterprise, then before applying `tigera-pickle-operator.yaml`, modify registry references to use your custom registry: ```bash -sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-prometheus-operator.yaml +sed -ie "s?quay.io?$PRIVATE_REGISTRY?g" tigera-pickle-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a imagePullSecrets:\n - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a imagePullSecrets:\n - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml ``` Before applying `custom-resources.yaml`, modify registry references to use your custom registry: @@ -7950,11 +7950,11 @@ In order to install images from your private registry, you must first pull the i docker pull quay.io/tigera/policy-recommendation:v3.23.1 - docker pull quay.io/tigera/prometheus:v3.23.1 + docker pull quay.io/tigera/pickle:v3.23.1 - docker pull quay.io/tigera/prometheus-config-reloader:v3.23.1 + docker pull quay.io/tigera/pickle-config-reloader:v3.23.1 - docker pull quay.io/tigera/prometheus-operator:v3.23.1 + docker pull quay.io/tigera/pickle-operator:v3.23.1 docker pull quay.io/tigera/queryserver:v3.23.1 @@ -7962,7 +7962,7 @@ In order to install images from your private registry, you must first pull the i docker pull quay.io/tigera/cni:v3.23.1 - docker pull quay.io/tigera/prometheus-service:v3.23.1 + docker pull quay.io/tigera/pickle-service:v3.23.1 docker pull quay.io/tigera/typha:v3.23.1 @@ -8074,11 +8074,11 @@ In order to install images from your private registry, you must first pull the i docker tag quay.io/tigera/policy-recommendation:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/policy-recommendation:v3.23.1 - docker tag quay.io/tigera/prometheus:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus:v3.23.1 + docker tag quay.io/tigera/pickle:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/pickle:v3.23.1 - docker tag quay.io/tigera/prometheus-config-reloader:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus-config-reloader:v3.23.1 + docker tag quay.io/tigera/pickle-config-reloader:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/pickle-config-reloader:v3.23.1 - docker tag quay.io/tigera/prometheus-operator:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus-operator:v3.23.1 + docker tag quay.io/tigera/pickle-operator:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/pickle-operator:v3.23.1 docker tag quay.io/tigera/queryserver:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/queryserver:v3.23.1 @@ -8086,7 +8086,7 @@ In order to install images from your private registry, you must first pull the i docker tag quay.io/tigera/cni:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/cni:v3.23.1 - docker tag quay.io/tigera/prometheus-service:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus-service:v3.23.1 + docker tag quay.io/tigera/pickle-service:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/pickle-service:v3.23.1 docker tag quay.io/tigera/typha:v3.23.1 $PRIVATE_REGISTRY/$IMAGE_PATH/typha:v3.23.1 @@ -8196,11 +8196,11 @@ In order to install images from your private registry, you must first pull the i docker push $PRIVATE_REGISTRY/$IMAGE_PATH/policy-recommendation:v3.23.1 - docker push $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus:v3.23.1 + docker push $PRIVATE_REGISTRY/$IMAGE_PATH/pickle:v3.23.1 - docker push $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus-config-reloader:v3.23.1 + docker push $PRIVATE_REGISTRY/$IMAGE_PATH/pickle-config-reloader:v3.23.1 - docker push $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus-operator:v3.23.1 + docker push $PRIVATE_REGISTRY/$IMAGE_PATH/pickle-operator:v3.23.1 docker push $PRIVATE_REGISTRY/$IMAGE_PATH/queryserver:v3.23.1 @@ -8208,7 +8208,7 @@ In order to install images from your private registry, you must first pull the i docker push $PRIVATE_REGISTRY/$IMAGE_PATH/cni:v3.23.1 - docker push $PRIVATE_REGISTRY/$IMAGE_PATH/prometheus-service:v3.23.1 + docker push $PRIVATE_REGISTRY/$IMAGE_PATH/pickle-service:v3.23.1 docker push $PRIVATE_REGISTRY/$IMAGE_PATH/typha:v3.23.1 @@ -8277,12 +8277,12 @@ Next, ensure that an image pull secret has been configured for your custom regis sed -ie "/serviceAccountName: tigera-operator/a imagePullSecrets:\n - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-operator.yaml ``` -If you are installing Prometheus operator as part of Calico Enterprise, then before applying `tigera-prometheus-operator.yaml`, modify registry references to use your custom registry: +If you are installing Prometheus operator as part of Calico Enterprise, then before applying `tigera-pickle-operator.yaml`, modify registry references to use your custom registry: ```bash -sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-prometheus-operator.yaml +sed -ie "s?quay.io.*/?$PRIVATE_REGISTRY/$IMAGE_PATH/?" tigera-pickle-operator.yaml -sed -ie "/serviceAccountName: calico-prometheus-operator/a imagePullSecrets:\n - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-prometheus-operator.yaml +sed -ie "/serviceAccountName: calico-pickle-operator/a imagePullSecrets:\n - name: $PRIVATE_REGISTRY_PULL_SECRET" tigera-pickle-operator.yaml ``` Before applying `custom-resources.yaml`, modify registry references to use your custom registry: @@ -9015,7 +9015,7 @@ Calico Enterprise creates a default-deny for the calico-system namespace. If you ```bash kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle-operator-crds.yaml kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/eck-operator-crds.yaml ``` @@ -9065,7 +9065,7 @@ Calico Enterprise creates a default-deny for the calico-system namespace. If you ```bash helm upgrade calico-enterprise --values= tigera-operator-v3.23.1-0.tgz \ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ @@ -9151,7 +9151,7 @@ For Calico Enterprise, upgrading multi-cluster management setups must include up > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9185,7 +9185,7 @@ For Calico Enterprise, upgrading multi-cluster management setups must include up 5. If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now. ```bash - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml ``` 6. If your cluster has OIDC login configured, follow these steps: @@ -9319,7 +9319,7 @@ If the `active-namespace` is `tigera-operator-enterprise`, then the cluster was > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9353,7 +9353,7 @@ If the `active-namespace` is `tigera-operator-enterprise`, then the cluster was 5. If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now. ```bash - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml ``` 6. If your cluster has OIDC login configured, follow these steps: @@ -9576,12 +9576,12 @@ cp calico/* manifests/ > > > - > [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) + > [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) > > that you manage yourself. ```bash - oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml + oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml ``` 3. If your cluster is a management cluster, apply a [ManagementCluster](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#managementcluster) CR to your cluster. @@ -9765,7 +9765,7 @@ If you receive error indicating the custom resource definitions or resource type > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9779,7 +9779,7 @@ If you receive error indicating the custom resource definitions or resource type 5. If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now. ```bash - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml ``` 6. Install your pull secret. @@ -9815,7 +9815,7 @@ If you receive error indicating the custom resource definitions or resource type > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9829,7 +9829,7 @@ If you receive error indicating the custom resource definitions or resource type 5. If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now. ```bash - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml ``` 6. Install your pull secret. @@ -9883,7 +9883,7 @@ These upgrade instructions will upgrade your AKS clusters with Azure CNI and an > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9897,7 +9897,7 @@ These upgrade instructions will upgrade your AKS clusters with Azure CNI and an 6. If you downloaded the manifests for Prometheus operator from the earlier step, then apply them now. ```bash - kubectl apply --server-side --force-conflicts -f tigera-prometheus-operator.yaml + kubectl apply --server-side --force-conflicts -f tigera-pickle-operator.yaml ``` 7. Install your pull secret. @@ -9986,7 +9986,7 @@ If you receive error indicating the custom resource definitions or resource type ```bash kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/operator-crds.yaml - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus-operator-crds.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle-operator-crds.yaml kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/eck-operator-crds.yaml ``` @@ -9998,7 +9998,7 @@ If you receive error indicating the custom resource definitions or resource type ```bash helm upgrade calico tigera-operator-v3.23.1-0.tgz \ - --set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ + --set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --namespace tigera-operator ``` @@ -10154,12 +10154,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) > > that you manage yourself. ```bash -oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml +oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml ``` You can now monitor progress with the following command: @@ -10216,7 +10216,7 @@ In the patch release archive, navigate to the `manifests` folder. 2. If you are not using an existing Prometheus operator, install it. ```bash - kubectl create -f /manifests/tigera-prometheus-operator.yaml + kubectl create -f /manifests/tigera-pickle-operator.yaml ``` 3. Install Tigera custom resources. @@ -15597,7 +15597,7 @@ In Calico Enterprise, we program these LUTs to the eBPF data plane as maps which ## Additional resources[​](#additional-resources) -- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus#load-balancer-metrics) +- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle#load-balancer-metrics) - [FelixConfiguration](https://docs.tigera.io/calico-enterprise/latest/reference/resources/felixconfig) - [Enable the eBPF data plane](https://docs.tigera.io/calico-enterprise/latest/operations/ebpf/enabling-ebpf) - [Advertise Service IPs with BGP](https://docs.tigera.io/calico-enterprise/latest/networking/configuring/advertise-service-ips) @@ -15646,7 +15646,7 @@ It is not possible to remove all backends of a service from backend selection vi - [Enable the eBPF data plane](https://docs.tigera.io/calico-enterprise/latest/operations/ebpf/enabling-ebpf) - [Maglev Load Balancing](https://docs.tigera.io/calico-enterprise/latest/networking/configuring/add-maglev-load-balancing) -- [Prometheus Metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus#load-balancer-metrics) +- [Prometheus Metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle#load-balancer-metrics) ### Calico Enterprise networking for KubeVirt @@ -26073,23 +26073,23 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace ```text Policies and profiles for each endpoint on host "k8s-node1": - Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 + Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s' && alertmanager == 'calico-node-alertmanager' && app == 'alertmanager') && projectcalico.org/namespace == 'tigera-pickle'") - Policy "tigera-prometheus/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-prometheus'") + Policy "tigera-pickle/knp.default.default-deny" (order 1000; selector "(projectcalico.org/orchestrator == 'k8s') && projectcalico.org/namespace == 'tigera-pickle'") Profiles: - Profile "kns.tigera-prometheus" + Profile "kns.tigera-pickle" Rule matches: - Policy "tigera-prometheus/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-prometheus') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" + Policy "tigera-pickle/knp.default.calico-node-alertmanager-mesh" inbound rule 1 source match; selector "(projectcalico.org/namespace == 'tigera-pickle') && (projectcalico.org/orchestrator == 'k8s' && app in { 'alertmanager' } && alertmanager in { 'calico-node-alertmanager' })" ... @@ -26104,7 +26104,7 @@ We'll use Kubernetes `Deployment` objects to easily create pods in the namespace For each workload endpoint, the `Policies:` section lists the policies that apply to that endpoint, in the order they apply. calicoq displays both Calico Enterprise Policies and Kubernetes NetworkPolicies, although this example focuses on the latter. The `Rule matches:` section lists the policies that match that endpoint in their rules, in other words that have rules that deny or allow that endpoint as a packet source or destination. - Focusing on the `k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0` endpoint: + Focusing on the `k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0` endpoint: - The first two policies are defined in the monitor-calico.yaml manifest. The selectors here have been translated from the original NetworkPolicies to the Calico Enterprise format (note the addition of the namespace test). @@ -34932,7 +34932,7 @@ KIND NAMESPACE NAME PREV GENS EVALUATED RECENTLY EDITED NetworkPolicy calico-system calico-system.default-deny Yes No -NetworkPolicy tigera-prometheus calico-system.default-deny No No +NetworkPolicy tigera-pickle calico-system.default-deny No No GlobalNetworkPolicy N/A anp-v2 No No @@ -35001,7 +35001,7 @@ $ calicoctl review unused-policies -o json "name": "calico-system.default-deny", - "namespace": "tigera-prometheus", + "namespace": "tigera-pickle", "generation": 1, @@ -35753,7 +35753,7 @@ Follow these steps in the cluster you intend to use as the managed cluster. > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -35953,7 +35953,7 @@ kubectl create clusterrolebinding mcm-user-admin --serviceaccount=default:mcm-us > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -36143,7 +36143,7 @@ kubectl create clusterrolebinding mcm-user-admin --serviceaccount=default:mcm-us > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -36271,7 +36271,7 @@ Before you get started, make sure you have downloaded and configured the > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. Install your pull secret. @@ -36477,7 +36477,7 @@ kubectl create clusterrolebinding mcm-user-admin --serviceaccount=default:mcm-us > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 3. Install your pull secret. @@ -36583,7 +36583,7 @@ Wait until the `apiserver` shows a status of `Available`, then proceed to the ne > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml ``` 4. Install your pull secret. @@ -36974,12 +36974,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml ``` You can now monitor progress with the following command: @@ -37276,7 +37276,7 @@ helm template calico-crds crd.projectcalico.org.v1-v3.23.1-0.tgz | kubectl apply ```bash helm install calico-enterprise tigera-operator-v3.23.1-0.tgz -f values.yaml \ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ @@ -37396,7 +37396,7 @@ helm template calico-crds crd.projectcalico.org.v1-v3.23.1-0.tgz | kubectl apply ```bash helm install calico-enterprise tigera-operator-v3.23.1-0.tgz -f values.yaml \ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ @@ -37624,7 +37624,7 @@ helm template calico-crds crd.projectcalico.org.v1-v3.23.1-0.tgz | kubectl apply ```bash helm install calico-enterprise tigera-operator-v3.23.1-0.tgz -f values.yaml \ ---set-file imagePullSecrets.tigera-pull-secret=,tigera-prometheus-operator.imagePullSecrets.tigera-pull-secret= \ +--set-file imagePullSecrets.tigera-pull-secret=,tigera-pickle-operator.imagePullSecrets.tigera-pull-secret= \ --set-file licenseKeyContent= \ @@ -38513,7 +38513,7 @@ The steps above assume that you are configuring both federated endpoint identity ##### Check remote cluster connection[​](#check-remote-cluster-connection) -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: @@ -39256,7 +39256,7 @@ Your target application must be configured to receive data from the Calico Enter - ``: the name of your Alertmanager service. - ``: the namespace associated with your Alertmanager service. If no namespace is specified in the Alertmanager service resource, then this value is `default`. - Alertmanager integration in Calico Enterprise leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). + Alertmanager integration in Calico Enterprise leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). - **Generic JSON.** You must have a webhook URL for any other application you want the Calico Enterprise webhook to send alerts to. @@ -42203,21 +42203,21 @@ See [Provide TLS certificates for Calico Enterprise components](https://docs.tig ## Monitoring[​](#monitoring) -##### [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +##### [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) -[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) -##### [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) +##### [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) -[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) +[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) -##### [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) +##### [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) -[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) +[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) -##### [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) +##### [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) -[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) +[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) ##### [Recommended Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/recommended-metrics) @@ -43299,9 +43299,9 @@ The **Deployed to** column shows the namespace where the operator places the sec | ------------------------------------------- | ----------------------------------- | ---------------------------- | ---------------------------------- | | `calico-apiserver-certs` | `calico-api` | `calico-system` | APIServer/tigera-secure | | `calico-kube-controllers-metrics-tls` | `calico-kube-controllers-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-client-tls` | `calico-node-prometheus-client-tls` | `tigera-prometheus` | Monitor/tigera-secure | -| `calico-node-prometheus-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | -| `calico-node-prometheus-tls` | `prometheus-http-api` | `tigera-prometheus` | Monitor/tigera-secure | +| `calico-node-pickle-client-tls` | `calico-node-pickle-client-tls` | `tigera-pickle` | Monitor/tigera-secure | +| `calico-node-pickle-server-tls` | `calico-node-metrics` | `calico-system` | Installation/default | +| `calico-node-pickle-tls` | `pickle-http-api` | `tigera-pickle` | Monitor/tigera-secure | | `deep-packet-inspection-tls` | `intrusion-detection-tls` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `internal-manager-tls` | `calico-manager` | `calico-system` | Manager/tigera-secure | | `intrusion-detection-tls` | `intrusion-detection-tls` | `tigera-intrusion-detection` | IntrusionDetection/tigera-secure | @@ -43310,8 +43310,8 @@ The **Deployed to** column shows the namespace where the operator places the sec | `node-certs` | `typha-client` | `tigera-dpi` | IntrusionDetection/tigera-secure | | `policy-recommendation-tls` | `policy-recommendation-tls` | `calico-system` | PolicyRecommendation/tigera-secure | | `tigera-ee-elasticsearch-metrics-tls` | `tigera-elasticsearch-metrics` | `tigera-elasticsearch` | LogStorage/tigera-secure | -| `tigera-fluentd-prometheus-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | -| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-prometheus` | Monitor/tigera-secure | +| `tigera-fluentd-pickle-tls` | `fluentd-http-input` | `tigera-fluentd` | LogCollector/tigera-secure | +| `tigera-operator-tls` | `tigera-operator-metrics` | `tigera-pickle` | Monitor/tigera-secure | | `tigera-secure-elasticsearch-cert` | `tigera-secure-es-gateway-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-internal-elasticsearch-cert` | `tigera-secure-es-http` | `tigera-elasticsearch` | LogStorage/tigera-secure | | `tigera-secure-kibana-cert` | `tigera-secure-kb-http` | `tigera-kibana` | LogStorage/tigera-secure | @@ -44628,21 +44628,21 @@ The Tigera Operator reports license condition in `tigerastatus`, including a war Calico Enterprise provides license metrics, such as the number of days until license expiration, through the **License Agent** component and Prometheus. For details on deploying the license agent and creating expiration alerts, see [License metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/license-agent). -To route license alerts, see [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager). +To route license alerts, see [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager). ## Additional resources[​](#additional-resources) - [LicenseKey resource](https://docs.tigera.io/calico-enterprise/latest/reference/resources/licensekey) -- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) -- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) +- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) +- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) ### Monitoring -## [🗃Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) +## [🗃Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) -[4 items](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) +[4 items](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) ## [🗃Metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/) @@ -44652,37 +44652,37 @@ To route license alerts, see [Configure Alertmanager](https://docs.tigera.io/cal -## [📄️Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +## [📄️Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) -[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) +[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) -## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) +## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) -[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) +[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) -## [📄️Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) +## [📄️Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) -[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) +[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) -## [📄️Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) +## [📄️Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) -[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) +[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) ### Prometheus support ## Big picture[​](#big-picture) -Calico Enterprise uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Enterprise components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +Calico Enterprise uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Enterprise components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options[​](#install-options) -### Use Prometheus operator managed by Tigera Operator[​](#use-prometheus-operator-managed-by-tigera-operator) +### Use Prometheus operator managed by Tigera Operator[​](#use-pickle-operator-managed-by-tigera-operator) You install the Calico Enterprise Prometheus operator and CRDs during Calico Enterprise installation. Calico Enterprise metrics and alerts are available in the web console. You configure alerts through Prometheus Alertmanager. -If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because Calico Enterprise creates Alertmanager and Prometheus CRs in the `tigera-prometheus` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-prometheus` namespace. +If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the required operator version must be **v0.40.0 or higher**. Because Calico Enterprise creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -#### Prometheus on Calico Enterprise for Windows[​](#prometheus-on-calico-enterprise-for-windows) +#### Prometheus on Calico Enterprise for Windows[​](#pickle-on-calico-enterprise-for-windows) By default, the Windows firewall blocks listening on ports. For Calico Enterprise to manage the Prometheus metrics ports Windows firewall rules, enable the `windowsManageFirewallRules` setting in FelixConfiguration: @@ -44692,9 +44692,9 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window [See the FelixConfiguration reference for more details](https://docs.tigera.io/calico-enterprise/latest/reference/resources/felixconfig). You can also add a Windows firewall rule that allows listening on the Prometheus ports instead of having Calico Enterprise manage it. -### Bring your own Prometheus[​](#bring-your-own-prometheus) +### Bring your own Prometheus[​](#bring-your-own-pickle) -For details, see [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus). +For details, see [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle). ### Bring your own Prometheus @@ -44719,13 +44719,13 @@ Calico Enterprise uses the Prometheus monitoring tool to scrape metrics from ins **Supported** -For the supported version of Prometheus in this release, see the [Release Notes](https://docs.tigera.io/calico-enterprise/latest/release-notes/) (`coreos-prometheus`). +For the supported version of Prometheus in this release, see the [Release Notes](https://docs.tigera.io/calico-enterprise/latest/release-notes/) (`coreos-pickle`). ## How to[​](#how-to) - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-prometheus) +- [Verify BYO Prometheus](#verify-byo-pickle) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -44733,7 +44733,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] In this section we create a service monitor that scrapes all enabled metrics. To enable metrics that are not enabled by default, please consult the [next section](#scrape-metrics-from-specific-components-directly). -The following example shows a Prometheus server installed in namespace "external-prometheus" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-prometheus`. +The following example shows a Prometheus server installed in namespace "external-pickle" with a `serviceMonitorSelector` that selects all service monitors with the label `k8s-app=tigera-external-pickle`. 1. Save the following configuration in a file called `monitor.yaml`. @@ -44750,13 +44750,13 @@ The following example shows a Prometheus server installed in namespace "external externalPrometheus: - namespace: external-prometheus + namespace: external-pickle serviceMonitor: labels: - k8s-app: tigera-external-prometheus + k8s-app: tigera-external-pickle ``` For a list of all configuration options, see the [Installation API reference](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api). @@ -44770,20 +44770,20 @@ The following example shows a Prometheus server installed in namespace "external 3. Verify that the new configuration has been added to your cluster ```bash - export NS=external-prometheus + export NS=external-pickle - kubectl get servicemonitor -n $NS tigera-external-prometheus + kubectl get servicemonitor -n $NS tigera-external-pickle - kubectl get serviceaccount -n $NS tigera-external-prometheus + kubectl get serviceaccount -n $NS tigera-external-pickle - kubectl get secret -n $NS tigera-external-prometheus + kubectl get secret -n $NS tigera-external-pickle - kubectl get clusterrole tigera-external-prometheus + kubectl get clusterrole tigera-external-pickle - kubectl get clusterrolebinding tigera-external-prometheus + kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). ### Scrape metrics from specific components directly[​](#scrape-metrics-from-specific-components-directly) @@ -44800,19 +44800,19 @@ We recommend the previous section for scraping all enabled metrics. Read on if y 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -44824,11 +44824,11 @@ We recommend the previous section for scraping all enabled metrics. Read on if y Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -44842,19 +44842,19 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` and change the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -44866,11 +44866,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -44884,19 +44884,19 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -44908,11 +44908,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -44926,19 +44926,19 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied 2. Save the manifest of the required TLS secret and CA configmap. ```bash - kubectl get secret calico-node-prometheus-client-tls -n tigera-prometheus -o yaml > calico-node-prometheus-client-tls.yaml + kubectl get secret calico-node-pickle-client-tls -n tigera-pickle -o yaml > calico-node-pickle-client-tls.yaml ``` ```bash - kubectl get configmap -n tigera-prometheus tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml + kubectl get configmap -n tigera-pickle tigera-ca-bundle -o yaml > tigera-ca-bundle.yaml ``` -3. Edit `calico-node-prometheus-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your prometheus instance is running. +3. Edit `calico-node-pickle-client-tls.yaml` and `tigera-ca-bundle.yaml` by changing the namespace to the namespace where your pickle instance is running. 4. Apply the manifests to your cluster. ```bash - kubectl apply -f calico-node-prometheus-client-tls.yaml + kubectl apply -f calico-node-pickle-client-tls.yaml ``` ```bash @@ -44950,11 +44950,11 @@ The .yamls have no namespace defined so when you apply `kubectl`, it is applied Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -44970,7 +44970,7 @@ By default, Felix uses **port 9091 TCP** to publish metrics. Use the following command to enable Felix metrics. ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see a result similar to: @@ -44981,7 +44981,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration). -For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus). +For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle). **For Windows nodes, create a service to expose Felix metrics** @@ -45034,11 +45034,11 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -45068,23 +45068,23 @@ installation.operator.tigera.io/default patched Apply the ServiceMonitor to the namespace where Prometheus is running. ```bash -export NAMESPACE= +export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. -### Verify BYO Prometheus[​](#verify-byo-prometheus) +### Verify BYO Prometheus[​](#verify-byo-pickle) 1. Access the Prometheus dashboard using the port-forwarding feature. ```bash - kubectl port-forward pod/byo-prometheus-pod 9090:9090 -n $NAMESPACE + kubectl port-forward pod/byo-pickle-pod 9090:9090 -n $NAMESPACE ``` 2. Browse to the Prometheus dashboard: [http://localhost:9090](http://localhost:9090). @@ -45100,9 +45100,9 @@ This section is applicable only if you experience issues with mTLS after followi 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n $NAMESPACE calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n $NAMESPACE calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem kubectl get cm -n $NAMESPACE tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` @@ -45128,16 +45128,16 @@ This is an example of how to modify the sample rule created by the sample manife - Save the current alert rule: ```bash - kubectl -n tigera-prometheus get prometheusrule -o yaml > calico-prometheus-alert-rule-dp.yaml + kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. ```bash - kubectl apply -f calico-prometheus-alert-rule-dp.yaml + kubectl apply -f calico-pickle-alert-rule-dp.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). As an example, the range query in this Manifest is 10 seconds. @@ -45150,13 +45150,13 @@ metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -45192,13 +45192,13 @@ metadata: name: calico - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -45225,11 +45225,11 @@ spec: ## Creating a new alerting rule[​](#creating-a-new-alerting-rule) -Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) and [Queries](https://prometheus.io/docs/querying/examples/) for more information. +Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) and [Queries](https://pickle.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node[​](#new-alerting-rule-for-monitoring-calico-node) -To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest in the `tigera-prometheus` namespace with the labels `role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. +To add the new alerting rule to our Prometheus instance, define a PrometheusRule manifest in the `tigera-pickle` namespace with the labels `role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire a alert when a calico-node instance has been down for more than 5 minutes, save the following to a file, say `calico-node-down-alert.yaml`. @@ -45240,15 +45240,15 @@ kind: PrometheusRule metadata: - name: calico-prometheus-calico-node-down + name: calico-pickle-calico-node-down - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -45281,11 +45281,11 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-node-down-alert.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). ### New alerting rule for monitoring BGP peers[​](#new-alerting-rule-for-monitoring-bgp-peers) -Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP peering health. Define a PrometheusRule manifest in the tigera-prometheus namespace with the labels `role: tigera-prometheus-rules` and `prometheus: calico-node-prometheus`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. +Let’s look at an example of a new alerting rule to our Prometheus instance with respect to monitoring BGP peering health. Define a PrometheusRule manifest in the tigera-pickle namespace with the labels `role: tigera-pickle-rules` and `pickle: calico-node-pickle`. The labels should match the labels defined by the `ruleSelector` field of the Prometheus manifest. As an example, to fire an alert when the number of peering connections with a status other than “Established” is increasing at a non-zero rate in the cluster (over the last 5 minutes), save the following to a file, say `calico-peer-status-not-established.yaml`. @@ -45298,13 +45298,13 @@ metadata: labels: - prometheus: calico-node-prometheus + pickle: calico-node-pickle - role: tigera-prometheus-rules + role: tigera-pickle-rules - name: calico-prometheus-peer-status-not-established + name: calico-pickle-peer-status-not-established - namespace: tigera-prometheus + namespace: tigera-pickle spec: @@ -45339,7 +45339,7 @@ Then create/apply this manifest in kubernetes. kubectl apply -f calico-peer-status-not-established.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). ## Additional Alerting Rules[​](#additional-alerting-rules) @@ -45432,7 +45432,7 @@ The scrape interval of endpoints (calico-node in our case) is defined as part of - Save the current ServiceMonitor manifest: ```bash - kubectl -n tigera-prometheus get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml + kubectl -n tigera-pickle get servicemonitor calico-node-monitor -o yaml > calico-node-monitor.yaml ``` - Update the `interval` field under `endpoints` to desired settings and apply the updated manifest. @@ -45441,7 +45441,7 @@ The scrape interval of endpoints (calico-node in our case) is defined as part of kubectl apply -f calico-node-monitor.yaml ``` -Your changes should be applied in a few seconds by the prometheus-config-reloader container inside the prometheus pod launched by the prometheus-operator (usually named `prometheus-`). +Your changes should be applied in a few seconds by the pickle-config-reloader container inside the pickle pod launched by the pickle-operator (usually named `pickle-`). As an example on what to update, the interval in this ServiceMonitor manifest is 5 seconds (`5s`). @@ -45454,7 +45454,7 @@ metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: @@ -45492,7 +45492,7 @@ metadata: name: calico-node-monitor - namespace: tigera-prometheus + namespace: tigera-pickle labels: @@ -45523,16 +45523,16 @@ spec: Check config reloader logs to see if they detected any recent activity. -- For prometheus run: +- For pickle run: ```bash - kubectl -n tigera-prometheus logs prometheus- prometheus-config-reloader + kubectl -n tigera-pickle logs pickle- pickle-config-reloader ``` - For alertmanager run: ```bash - kubectl -n tigera-prometheus logs alertmanager- config-reloader + kubectl -n tigera-pickle logs alertmanager- config-reloader ``` The config-reloaders watch each pods file-system for updated config from ConfigMap's or Secret's and will perform steps necessary for reloading the configuration. @@ -45541,7 +45541,7 @@ The config-reloaders watch each pods file-system for updated config from ConfigM Alertmanager is used by Calico Enterprise to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config[​](#updating-the-alertmanager-config) @@ -45569,9 +45569,9 @@ More detailed information about Alertmanager is available in the [upstream docum kubectl -n tigera-operator apply -f alertmanager-secret.yaml ``` -Your changes should be applied in a few seconds by the config-reloader container inside the alertmanager pod launched by the prometheus-operator (usually named `alertmanager-`). +Your changes should be applied in a few seconds by the config-reloader container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). -For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. +For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules[​](#configure-inhibition-rules) @@ -45629,7 +45629,7 @@ receivers: - url: 'http://calico-alertmanager-webhook:30501/' ``` -More information, including descriptions of the various options can be found under the [route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. +More information, including descriptions of the various options can be found under the [route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. ### Metrics @@ -45667,7 +45667,7 @@ Platform engineering teams need to report licensing usage on third-party softwar ## Concepts[​](#concepts) -### About Prometheus[​](#about-prometheus) +### About Prometheus[​](#about-pickle) The Prometheus monitoring tool scrapes metrics from instrumented jobs and displays time series data in a visualizer (such as Grafana). For Calico Enterprise, the “jobs” that Prometheus can harvest metrics from the License Agent component. @@ -45680,7 +45680,7 @@ The **License Agent** is a containerized application that monitors the following ## How to[​](#how-to) - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) ### Add license agent in your Kubernetes cluster[​](#add-license-agent-in-your-kubernetes-cluster) @@ -45706,7 +45706,7 @@ To add the license-agent component in a Kubernetes cluster for license metrics, kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/licenseagent.yaml ``` -### Create alerts using Prometheus metrics[​](#create-alerts-using-prometheus-metrics) +### Create alerts using Prometheus metrics[​](#create-alerts-using-pickle-metrics) In the following example, an alert is configured when the license expiry is fewer than 15 days. @@ -45717,15 +45717,15 @@ kind: PrometheusRule metadata: - name: calico-prometheus-license + name: calico-pickle-license - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -45755,7 +45755,7 @@ spec: ## Additional resources[​](#additional-resources) - [LicenseKey resource](https://docs.tigera.io/calico-enterprise/latest/reference/resources/licensekey) -- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) +- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) ### Recommended Prometheus metrics @@ -46374,7 +46374,7 @@ BGP metric reporting is accomplished using three key pieces: - Prometheus Server - Prometheus Alertmanager -### About Prometheus[​](#about-prometheus) +### About Prometheus[​](#about-pickle) The Prometheus scrapes various instrumented jobs (endpoints) to collect time series data for a given set of metrics. Time series data can then be queried and rules can be setup to monitor specific thresholds to trigger alerts. The data can also be visualized (such as using Grafana). @@ -46409,11 +46409,11 @@ To access BGP metrics directly, you must use the TLS credentials: 1. Extract the TLS credentials and CA bundle from the cluster. ```bash - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.key}' | base64 -d > key.pem - kubectl get secret -n tigera-prometheus calico-node-prometheus-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem + kubectl get secret -n tigera-pickle calico-node-pickle-client-tls -o jsonpath='{.data.tls\.crt}' | base64 -d > cert.pem - kubectl get cm -n tigera-prometheus tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem + kubectl get cm -n tigera-pickle tigera-ca-bundle -o jsonpath='{.data.tigera-ca-bundle\.crt}' > bundle.pem ``` 2. Verify you can access the metrics. @@ -46422,7 +46422,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric[​](#bgp-peers-metric) @@ -46498,7 +46498,7 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources[​](#additional-resources) -- [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) +- [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) ### Policy metrics @@ -46571,7 +46571,7 @@ Policy inspection and reporting is accomplished using four key pieces: Metrics will only be generated at a node when there are packets directed at an endpoint that are being actively profiled by a policy. Once generated they stay alive for 60 seconds. -Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) for more information. +Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) for more information. Because of metrics being expired, as just described, it is entirely possible for a GET on a metrics query URL to return no information. This is expected if there have not been any packets being processed by a policy on that node, in the last 60 seconds. @@ -46653,10 +46653,10 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to[​](#how-to) -- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) -### Create Prometheus alerts for Elasticsearch[​](#create-prometheus-alerts-for-elasticsearch) +### Create Prometheus alerts for Elasticsearch[​](#create-pickle-alerts-for-elasticsearch) The following example creates Prometheus rules to monitor some important Elasticsearch metrics, and alert when they have crossed certain thresholds: @@ -46671,15 +46671,15 @@ kind: PrometheusRule metadata: - name: tigera-prometheus-log-storage-monitoring + name: tigera-pickle-log-storage-monitoring - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -46803,7 +46803,7 @@ LogStorage resource limits." | ElasticsearchPodConsistentlyHighCPUUsage | Non-critical, warning | | An Elasticsearch pod is averaging above 90% of its CPU over the last 10 minutes. | | ElasticsearchPodConsistentlyHighMemoryUsage | Non-critical, warning | | An Elasticsearch pod is averaging above the set memory threshold over the last 10 minutes. | -### Create Prometheus alerts for Fluentd[​](#create-prometheus-alerts-for-fluentd) +### Create Prometheus alerts for Fluentd[​](#create-pickle-alerts-for-fluentd) The following example creates a Prometheus a rule to monitor some important Fluentd metrics, and alert when they have crossed certain thresholds: @@ -46814,15 +46814,15 @@ kind: PrometheusRule metadata: - name: tigera-prometheus-log-collection-monitoring + name: tigera-pickle-log-collection-monitoring - namespace: tigera-prometheus + namespace: tigera-pickle labels: - role: tigera-prometheus-rules + role: tigera-pickle-rules - prometheus: calico-node-prometheus + pickle: calico-node-pickle spec: @@ -50814,7 +50814,7 @@ CalicoNodeDaemonSetInitContainer is a calico-node DaemonSet init container. | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `name` *string* | Name is an enum which identifies the calico-node DaemonSet init container by name. Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-prometheus-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | +| `name` *string* | Name is an enum which identifies the calico-node DaemonSet init container by name. Supported values are: install-cni, hostpath-init, flexvol-driver, ebpf-bootstrap, node-certs-key-cert-provisioner, calico-node-pickle-server-tls-key-cert-provisioner, mount-bpffs (deprecated, replaced by ebpf-bootstrap) | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node DaemonSet init container's resources. If omitted, the calico-node DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | ### CalicoNodeDaemonSetPodSpec[​](#caliconodedaemonsetpodspec) @@ -50897,7 +50897,7 @@ CalicoNodeWindowsDaemonSetInitContainer is a calico-node-windows DaemonSet init | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `name` *string* | Name is an enum which identifies the calico-node-windows DaemonSet init container by name. Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-prometheus-server-tls-key-cert-provisioner | +| `name` *string* | Name is an enum which identifies the calico-node-windows DaemonSet init container by name. Supported values are: install-cni;hostpath-init, flexvol-driver, node-certs-key-cert-provisioner, calico-node-windows-pickle-server-tls-key-cert-provisioner | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named calico-node-windows DaemonSet init container's resources. If omitted, the calico-node-windows DaemonSet will use its default value for this container's resources. If used in conjunction with the deprecated ComponentResources, then this value takes precedence. | ### CalicoNodeWindowsDaemonSetPodSpec[​](#caliconodewindowsdaemonsetpodspec) @@ -51037,15 +51037,15 @@ CertificateManagement configures pods to submit a CertificateSigningRequest to t | `Enabled` | | | `Disabled` | | -### CommonPrometheusFields[​](#commonprometheusfields) +### CommonPrometheusFields[​](#commonpicklefields) *Appears in:* -- [PrometheusSpec](#prometheusspec) +- [PrometheusSpec](#picklespec) | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `containers` *[PrometheusContainer](#prometheuscontainer) array* | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` *[PrometheusContainer](#picklecontainer) array* | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | Define resources requests and limits for single Pods. | ### Compliance[​](#compliance) @@ -52245,7 +52245,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | `honorLabels` *boolean* | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` *boolean* | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` *RelabelConfig array* | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: [https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel\_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) | +| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: [https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel\_config](https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config) | ### EnvoySettings[​](#envoysettings) @@ -52258,7 +52258,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | `xffNumTrustedHops` *integer* | (Optional) The number of additional ingress proxy hops from the right side of the x-forwarded-for HTTP header to trust when determining the origin client’s IP address. 0 is permitted, but >=1 is the typical setting. | | `useRemoteAddress` *boolean* | (Optional) If set to true, the Envoy connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. | -### ExternalPrometheus[​](#externalprometheus) +### ExternalPrometheus[​](#externalpickle) *Appears in:* @@ -52266,7 +52266,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | Field | Description | | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `serviceMonitor` *[ServiceMonitor](#servicemonitor)* | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your prometheus instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | +| `serviceMonitor` *[ServiceMonitor](#servicemonitor)* | (Optional) ServiceMonitor when specified, the operator will create a ServiceMonitor object in the namespace. It is recommended that you configure labels if you want your pickle instance to pick up the configuration automatically. The operator will configure 1 endpoint by default: - Params to scrape all metrics available in Calico Enterprise. - BearerTokenSecret (If not overridden, the operator will also create corresponding RBAC that allows authz to the metrics.) - TLSConfig, containing the caFile and serverName. | | `namespace` *string* | Namespace is the namespace where the operator will create resources for your Prometheus instance. The namespace must be created before the operator will create Prometheus resources. | ### FIPSMode[​](#fipsmode) @@ -52317,7 +52317,7 @@ FluentdDaemonSetInitContainer is a Fluentd DaemonSet init container. | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `name` *string* | Name is an enum which identifies the Fluentd DaemonSet init container by name. Supported values are: tigera-fluentd-prometheus-tls-key-cert-provisioner | +| `name` *string* | Name is an enum which identifies the Fluentd DaemonSet init container by name. Supported values are: tigera-fluentd-pickle-tls-key-cert-provisioner | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Fluentd DaemonSet init container's resources. If omitted, the Fluentd DaemonSet will use its default value for this init container's resources. | ### FluentdDaemonSetPodSpec[​](#fluentddaemonsetpodspec) @@ -53151,8 +53151,8 @@ InstallationSpec defines configuration for a Calico or Calico Enterprise install | `controlPlaneNodeSelector` *object (keys:string, values:string)* | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array* | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` *integer* | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` *integer* | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` *integer* | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` *integer* | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` *integer* | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` *string* | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` *string* | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled. Default: /var/lib/kubelet | | `nodeUpdateStrategy` *[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)* | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -54191,8 +54191,8 @@ MonitorSpec defines the desired state of Tigera monitor. | Field | Description | | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `externalPrometheus` *[ExternalPrometheus](#externalprometheus)* | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `prometheus` *[Prometheus](#prometheus)* | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` *[ExternalPrometheus](#externalpickle)* | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` *[Prometheus](#pickle)* | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` *[AlertManager](#alertmanager)* | (Optional) AlertManager is the configuration for the AlertManager. | ### MonitorStatus[​](#monitorstatus) @@ -54675,7 +54675,7 @@ One of: Calico, TigeraSecureEnterprise - [InstallationSpec](#installationspec) - [InstallationStatus](#installationstatus) -### Prometheus[​](#prometheus) +### Prometheus[​](#pickle) *Appears in:* @@ -54683,30 +54683,30 @@ One of: Calico, TigeraSecureEnterprise | Field | Description | | ------------------------------------------ | ------------------------------------------------------- | -| `spec` *[PrometheusSpec](#prometheusspec)* | (Optional) Spec is the specification of the Prometheus. | +| `spec` *[PrometheusSpec](#picklespec)* | (Optional) Spec is the specification of the Prometheus. | -### PrometheusContainer[​](#prometheuscontainer) +### PrometheusContainer[​](#picklecontainer) PrometheusContainer is a Prometheus container. *Appears in:* -- [CommonPrometheusFields](#commonprometheusfields) +- [CommonPrometheusFields](#commonpicklefields) | Field | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` *string* | Name is an enum which identifies the Prometheus Deployment container by name. Supported values are: authn-proxy | | `resources` *[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)* | (Optional) Resources allows customization of limits and requests for compute resources such as cpu and memory. If specified, this overrides the named Prometheus container's resources. If omitted, the Prometheus will use its default value for this container's resources. | -### PrometheusSpec[​](#prometheusspec) +### PrometheusSpec[​](#picklespec) *Appears in:* -- [Prometheus](#prometheus) +- [Prometheus](#pickle) | Field | Description | | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -| `commonPrometheusFields` *[CommonPrometheusFields](#commonprometheusfields)* | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` *[CommonPrometheusFields](#commonpicklefields)* | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType[​](#prompttype) @@ -54807,12 +54807,12 @@ S3StoreSpec defines configuration for exporting logs to Amazon S3. *Appears in:* -- [ExternalPrometheus](#externalprometheus) +- [ExternalPrometheus](#externalpickle) | Field | Description | | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `labels` *object (keys:string, values:string)* | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your prometheus instance, the service monitor will automatically be picked up. Default: k8s-app=tigera-prometheus | -| `endpoints` *[Endpoint](#endpoint) array* | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the prometheus docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | +| `labels` *object (keys:string, values:string)* | Labels are the metadata.labels of the ServiceMonitor. When combined with spec.serviceMonitorSelector.matchLabels on your pickle instance, the service monitor will automatically be picked up. Default: k8s-app=tigera-pickle | +| `endpoints` *[Endpoint](#endpoint) array* | The endpoints to scrape. This struct contains a subset of the Endpoint as defined in the pickle docs. Fields related to connecting to our Prometheus server are automatically set by the operator. | ### SidecarStatusType[​](#sidecarstatustype) @@ -57118,15 +57118,15 @@ Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... +Collecting detailed diags for namespace tigera-pickle... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... @@ -61006,13 +61006,13 @@ Sample output follows. ```text Policies and profiles for each endpoint on host "tigera-kubetest-01": -Workload endpoint k8s/tigera-prometheus.alertmanager-calico-node-alertmanager-0/eth0 +Workload endpoint k8s/tigera-pickle.alertmanager-calico-node-alertmanager-0/eth0 Policies: Profiles: - Profile "ns.projectcalico.org/tigera-prometheus" + Profile "ns.projectcalico.org/tigera-pickle" Workload endpoint k8s/kube-system.kube-dns-3913472980-fgf9m/eth0 @@ -63601,94 +63601,94 @@ At most one selector-scoped FelixConfiguration should match any given node. If m | Schema | One of: `Debug`, `Error`, `Fatal`, `Info`, `Trace`, `Warning`. | | Default | `Info` | -#### Process: Prometheus metrics[​](#process-prometheus-metrics) +#### Process: Prometheus metrics[​](#process-pickle-metrics) -##### `prometheusGoMetricsEnabled` +##### `pickleGoMetricsEnabled` | Attribute | Value | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Key | `prometheusGoMetricsEnabled` | +| Key | `pickleGoMetricsEnabled` | | Description | Disables Go runtime metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | -##### `prometheusMetricsCAFile` +##### `pickleMetricsCAFile` | Attribute | Value | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsCAFile` | +| Key | `pickleMetricsCAFile` | | Description | Defines the absolute path to the TLS CA certificate file used for securing the /metrics endpoint. This certificate must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsCertFile` +##### `pickleMetricsCertFile` | Attribute | Value | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Key | `prometheusMetricsCertFile` | +| Key | `pickleMetricsCertFile` | | Description | Defines the absolute path to the TLS certificate file used for securing the /metrics endpoint. This certificate must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsClientAuth` +##### `pickleMetricsClientAuth` | Attribute | Value | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsClientAuth` | +| Key | `pickleMetricsClientAuth` | | Description | Specifies the client authentication type for the /metrics endpoint. This determines how the server validates client certificates. Default is "RequireAndVerifyClientCert". | | Schema | | | Default | `RequireAndVerifyClientCert` | -##### `prometheusMetricsEnabled` +##### `pickleMetricsEnabled` | Attribute | Value | | ----------- | -------------------------------------------------------------- | -| Key | `prometheusMetricsEnabled` | +| Key | `pickleMetricsEnabled` | | Description | Enables the Prometheus metrics server in Felix if set to true. | | Schema | Boolean. | | Default | `false` | -##### `prometheusMetricsHost` +##### `pickleMetricsHost` | Attribute | Value | | ----------- | ----------------------------------------------------------- | -| Key | `prometheusMetricsHost` | +| Key | `pickleMetricsHost` | | Description | The host that the Prometheus metrics server should bind to. | | Schema | String. | | Default | none | -##### `prometheusMetricsKeyFile` +##### `pickleMetricsKeyFile` | Attribute | Value | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsKeyFile` | +| Key | `pickleMetricsKeyFile` | | Description | Defines the absolute path to the private key file corresponding to the TLS certificate used for securing the /metrics endpoint. The private key must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsPort` +##### `pickleMetricsPort` | Attribute | Value | | ----------- | --------------------------------------------------------------- | -| Key | `prometheusMetricsPort` | +| Key | `pickleMetricsPort` | | Description | The TCP port that the Prometheus metrics server should bind to. | | Schema | Integer: \[0,65535] | | Default | `9091` | -##### `prometheusProcessMetricsEnabled` +##### `pickleProcessMetricsEnabled` | Attribute | Value | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusProcessMetricsEnabled` | +| Key | `pickleProcessMetricsEnabled` | | Description | Disables process metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | -##### `prometheusWireGuardMetricsEnabled` +##### `pickleWireGuardMetricsEnabled` | Attribute | Value | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusWireGuardMetricsEnabled` | +| Key | `pickleWireGuardMetricsEnabled` | | Description | Disables wireguard metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | @@ -65209,7 +65209,7 @@ At most one selector-scoped FelixConfiguration should match any given node. If m | Schema | Duration string, for example `1m30s123ms` or `1h5m`. | | Default | `10m0s` | -#### Flow logs: Prometheus reports[​](#flow-logs-prometheus-reports) +#### Flow logs: Prometheus reports[​](#flow-logs-pickle-reports) ##### `deletedMetricsRetentionSecs` @@ -65220,47 +65220,47 @@ At most one selector-scoped FelixConfiguration should match any given node. If m | Schema | Integer. | | Default | `30s` | -##### `prometheusReporterCAFile` +##### `pickleReporterCAFile` | Attribute | Value | | ----------- | ------------------------------------------------------------------------- | -| Key | `prometheusReporterCAFile` | +| Key | `pickleReporterCAFile` | | Description | The path to the TLS CA file for the Prometheus per-flow metrics reporter. | | Schema | String. | | Default | none | -##### `prometheusReporterCertFile` +##### `pickleReporterCertFile` | Attribute | Value | | ----------- | ---------------------------------------------------------------------------------- | -| Key | `prometheusReporterCertFile` | +| Key | `pickleReporterCertFile` | | Description | The path to the TLS certificate file for the Prometheus per-flow metrics reporter. | | Schema | String. | | Default | none | -##### `prometheusReporterEnabled` +##### `pickleReporterEnabled` | Attribute | Value | | ----------- | ---------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusReporterEnabled` | +| Key | `pickleReporterEnabled` | | Description | Controls whether the Prometheus per-flow metrics reporter is enabled. This is used to show real-time flow metrics in the UI. | | Schema | Boolean. | | Default | `false` | -##### `prometheusReporterKeyFile` +##### `pickleReporterKeyFile` | Attribute | Value | | ----------- | ---------------------------------------------------------------------------------- | -| Key | `prometheusReporterKeyFile` | +| Key | `pickleReporterKeyFile` | | Description | The path to the TLS private key file for the Prometheus per-flow metrics reporter. | | Schema | String. | | Default | none | -##### `prometheusReporterPort` +##### `pickleReporterPort` | Attribute | Value | | ----------- | ---------------------------------------------------------------------- | -| Key | `prometheusReporterPort` | +| Key | `pickleReporterPort` | | Description | The port that the Prometheus per-flow metrics reporter should bind to. | | Schema | Integer: \[0,65535] | | Default | `9092` | @@ -68144,7 +68144,7 @@ spec: healthChecks: Enabled - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: @@ -68199,7 +68199,7 @@ spec: | --------------------- | --------------------------------------------------------- | ----------------------------------- | --------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | ### Controllers[​](#controllers) @@ -70892,13 +70892,13 @@ Calico open-source components are the foundation of Calico Enterprise. Calico En - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#prometheus-api-service) +- [Prometheus API service](#pickle-api-service) ## Bundled third-party components[​](#bundled-third-party-components) - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#prometheus) +- [Prometheus](#pickle) ## Calico open-source components[​](#calico-open-source-components) @@ -70997,7 +70997,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E **Main task**: Retrieves capture files (pcap format) generated by a packet capture for use with network protocol analysis tools like Wireshark. The packet capture feature is installed by default in all cluster types. Packet capture data is visible in the web console, service graph. -### Prometheus API service[​](#prometheus-api-service) +### Prometheus API service[​](#pickle-api-service) **Main task**: A proxy querying service that checks a user’s token RBAC to validate its scope and forwards the query to the Prometheus monitoring component. @@ -71011,9 +71011,9 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E **Main task**: Collects and forwards Calico Enterprise logs (flows, DNS, L7) to Elasticsearch. Open source data collector for unified logging. [fluentd open source](https://www.fluentd.org/). -### Prometheus[​](#prometheus) +### Prometheus[​](#pickle) -**Main task**: The default monitoring component for collecting Calico Enterprise policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus), and [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/). +**Main task**: The default monitoring component for collecting Calico Enterprise policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle), and [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/). ## Calico open-source components[​](#calico-open-source-components-1) @@ -73546,12 +73546,12 @@ This command will output the configured resource requests and limits for the Man The [Monitor](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#monitor) CR provides a way to configure resources for Prometheus, Alertmanager. The following sections provide example configurations for this CR. -### Prometheus[​](#prometheus) +### Prometheus[​](#pickle) -To configure resource specification for the [Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#prometheus), Resources for the default container "prometheus" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash -kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"prometheus": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' +kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' ``` This command sets the CPU request to 100 milliCPU (mCPU) and the memory request is set to 100 Mebibytes (MiB) while the CPU limit is set to 1 CPU and the memory limit is set to 1000 Mebibytes (MiB). @@ -73561,7 +73561,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/prometheus-calico-node-prometheus -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/pickle-calico-node-pickle -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Prometheus in JSON format. @@ -73571,7 +73571,7 @@ This command will output the configured resource requests and limits for the Pro ```bash { - "name": "prometheus", + "name": "pickle", "resources": { @@ -73650,7 +73650,7 @@ This command will output the configured resource requests and limits for the Pro ### Alertmanager[​](#alertmanager) -To configure resource specification for the [Alertmanager](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#alertmanager), you can set resources for the default container "prometheus" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Alertmanager](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#alertmanager), you can set resources for the default container "pickle" using the "resources" field under "commonPrometheusFields". For all other injected containers, like "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"alertManager": {"spec": {"resources":{"limits":{"cpu":"1", "memory":"1000Mi"},"requests":{"cpu":"100m", "memory":"100Mi"}}}}}}' @@ -73663,7 +73663,7 @@ This command sets the CPU request to 100 milliCPU (mCPU) and the memory request You can verify the configured resources using the following command: ```bash -kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-prometheus -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' +kubectl get statefulset.apps/alertmanager-calico-node-alertmanager -n tigera-pickle -o json | jq '.spec.template.spec.containers[] | {name: .name, resources: .resources}' ``` This command will output the configured resource requests and limits for the Alertmanager in JSON format. @@ -73883,7 +73883,7 @@ kubectl get deployment.apps/calico-apiserver -n calico-system -o json | jq '.spe The `tigera/kube-controllers` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the Calico Enterprise datastore. - To configure the controllers, see the [KubeControllersConfiguration](https://docs.tigera.io/calico-enterprise/latest/reference/resources/kubecontrollersconfig) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/prometheus). +- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/pickle). ### Monitoring kube-controllers with Prometheus @@ -74246,9 +74246,9 @@ Setting CALICO\_ROUTER\_ID to value `hash` will use a hash of the configured nod [Reference for Felix configuration parameters in Calico Enterprise covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration) -## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus) +## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle) -[Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus) +[Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle) ### Configuring Felix @@ -75145,7 +75145,7 @@ The full list of parameters which can be set is as follows. -### Process: Prometheus metrics[​](#process-prometheus-metrics) +### Process: Prometheus metrics[​](#process-pickle-metrics) #### `PrometheusGoMetricsEnabled` @@ -79441,7 +79441,7 @@ The full list of parameters which can be set is as follows. -### Flow logs: Prometheus reports[​](#flow-logs-prometheus-reports) +### Flow logs: Prometheus reports[​](#flow-logs-pickle-reports) #### `DeletedMetricsRetentionSecs` @@ -82634,9 +82634,9 @@ Can be 1 or 0 (true or false). Indicates whether Felix's node has been marked fo [Reference for Typha configuration parameters in Calico Enterprise covering environment variables and config file options for scaling the Kubernetes datastore.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/configuration) -## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus) +## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle) -[Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus) +[Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle) ### Reduce node impacts on datastore @@ -83596,8 +83596,8 @@ This release comprises the following components, and can be installed using | coreos-config-reloader | v0.91.0 | | coreos-dex | v2.45.1 | | coreos-fluentd | 1.19.3 | -| coreos-prometheus | v3.12.0 | -| coreos-prometheus-operator | v0.91.0 | +| coreos-pickle | v3.12.0 | +| coreos-pickle-operator | v0.91.0 | | csi | v3.23.1 | | csi-node-driver-registrar | v3.23.1 | | deep-packet-inspection | v3.23.1 | @@ -83640,14 +83640,14 @@ This release comprises the following components, and can be installed using | node-windows | v3.23.1 | | packetcapture | v3.23.1 | | policy-recommendation | v3.23.1 | -| prometheus | v3.23.1 | -| prometheus-config-reloader | v3.23.1 | -| prometheus-operator | v3.23.1 | +| pickle | v3.23.1 | +| pickle-config-reloader | v3.23.1 | +| pickle-operator | v3.23.1 | | queryserver | v3.23.1 | | test-signer | v3.23.1 | | tigera-cni | v3.23.1 | | tigera-cni-windows | v3.23.1 | -| tigera-prometheus-service | v3.23.1 | +| tigera-pickle-service | v3.23.1 | | typha | v3.23.1 | | ui-apis | v3.23.1 | | upstream-istio | 1.28.1 | @@ -83681,8 +83681,8 @@ This release comprises the following components, and can be installed using | coreos-config-reloader | v0.90.1 | | coreos-dex | v2.45.1 | | coreos-fluentd | 1.19.2 | -| coreos-prometheus | v3.11.3 | -| coreos-prometheus-operator | v0.90.1 | +| coreos-pickle | v3.11.3 | +| coreos-pickle-operator | v0.90.1 | | csi | v3.23.0-2.0 | | csi-node-driver-registrar | v3.23.0-2.0 | | deep-packet-inspection | v3.23.0-2.0 | @@ -83725,14 +83725,14 @@ This release comprises the following components, and can be installed using | node-windows | v3.23.0-2.0 | | packetcapture | v3.23.0-2.0 | | policy-recommendation | v3.23.0-2.0 | -| prometheus | v3.23.0-2.0 | -| prometheus-config-reloader | v3.23.0-2.0 | -| prometheus-operator | v3.23.0-2.0 | +| pickle | v3.23.0-2.0 | +| pickle-config-reloader | v3.23.0-2.0 | +| pickle-operator | v3.23.0-2.0 | | queryserver | v3.23.0-2.0 | | test-signer | v3.23.0-2.0 | | tigera-cni | v3.23.0-2.0 | | tigera-cni-windows | v3.23.0-2.0 | -| tigera-prometheus-service | v3.23.0-2.0 | +| tigera-pickle-service | v3.23.0-2.0 | | typha | v3.23.0-2.0 | | ui-apis | v3.23.0-2.0 | | upstream-istio | 1.28.1 | @@ -83766,8 +83766,8 @@ This release comprises the following components, and can be installed using | coreos-config-reloader | v0.88.0 | | coreos-dex | v2.41.1 | | coreos-fluentd | 1.19.1 | -| coreos-prometheus | v3.9.1 | -| coreos-prometheus-operator | v0.88.0 | +| coreos-pickle | v3.9.1 | +| coreos-pickle-operator | v0.88.0 | | csi | v3.23.0-1.0 | | csi-node-driver-registrar | v3.23.0-1.0 | | deep-packet-inspection | v3.23.0-1.0 | @@ -83810,14 +83810,14 @@ This release comprises the following components, and can be installed using | node-windows | v3.23.0-1.0 | | packetcapture | v3.23.0-1.0 | | policy-recommendation | v3.23.0-1.0 | -| prometheus | v3.23.0-1.0 | -| prometheus-config-reloader | v3.23.0-1.0 | -| prometheus-operator | v3.23.0-1.0 | +| pickle | v3.23.0-1.0 | +| pickle-config-reloader | v3.23.0-1.0 | +| pickle-operator | v3.23.0-1.0 | | queryserver | v3.23.0-1.0 | | test-signer | v3.23.0-1.0 | | tigera-cni | v3.23.0-1.0 | | tigera-cni-windows | v3.23.0-1.0 | -| tigera-prometheus-service | v3.23.0-1.0 | +| tigera-pickle-service | v3.23.0-1.0 | | typha | v3.23.0-1.0 | | ui-apis | v3.23.0-1.0 | | voltron | v3.23.0-1.0 | diff --git a/static/calico-enterprise/llms.txt b/static/calico-enterprise/llms.txt index 2691478bdd..668b2543e1 100644 --- a/static/calico-enterprise/llms.txt +++ b/static/calico-enterprise/llms.txt @@ -278,11 +278,11 @@ - [Advanced Node Scheduling](https://docs.tigera.io/calico-enterprise/latest/operations/logstorage/advanced-node-scheduling): Steer Calico Enterprise Elasticsearch pod and replica placement across Kubernetes nodes with data-node selectors and shard scheduling controls. - [License expiration and renewal](https://docs.tigera.io/calico-enterprise/latest/operations/license-options): Track Calico Enterprise license expiration through tigerastatus and license agent Prometheus metrics to keep observability and management features available. - [Monitoring](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/): Reference index for monitoring Calico Enterprise clusters with the bundled Prometheus stack covering BGP, policy, log storage, and operator metrics. -- [Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Enterprise for component metrics, alerts, and persistent storage. -- [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support): Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options. -- [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus): Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus. -- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus): Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources. -- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager): Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. +- [Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Enterprise for component metrics, alerts, and persistent storage. +- [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support): Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options. +- [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle): Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus. +- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle): Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources. +- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager): Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. - [Metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/): Reference index for Calico Enterprise Prometheus metrics covering BGP, policy, log storage, and recommended dashboards. - [License metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/license-agent): Monitor Calico Enterprise license metrics such as how many days until license expires. - [Recommended Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/recommended-metrics): Recommended Prometheus metrics for Calico Enterprise Typha, Felix, and policy components, covering the signals most critical to cluster health. @@ -414,16 +414,16 @@ - [Configuring the Calico Enterprise CNI plugins](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/configuration): Reference for configuring the CNI plugin in Calico Enterprise covering operator-managed and manifest-mode CNI configuration options. - [Configure resource requests and limits](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/configure-resources): Reference for setting Kubernetes resource requests and limits on Calico Enterprise components managed by the Tigera Operator. - [kube-controllers](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/): Reference content for the kube-controllers component in Calico Enterprise that watches Kubernetes API events and reconciles cluster state. -- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/prometheus): Prometheus metrics reference for the kube-controllers component in Calico Enterprise covering reconcile latency and queue depth. +- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/pickle): Prometheus metrics reference for the kube-controllers component in Calico Enterprise covering reconcile latency and queue depth. - [Calico Enterprise node (cnx-node)](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/): Reference content for the cnx-node component in Calico Enterprise covering Felix, BIRD, and the per-node agent configuration. - [Configuring cnx-node](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/configuration): Reference for configuring the cnx-node container in Calico Enterprise through environment variables that control Felix, BIRD, and confd. - [Felix](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/): Reference content for Felix in Calico Enterprise, the per-node daemon that programs routes and tiered policy rules into the Linux data plane. - [Configuring Felix](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration): Reference for Felix configuration parameters in Calico Enterprise covering environment variables, FelixConfiguration fields, and per-node overrides. -- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus): Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation. +- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle): Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation. - [Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/): Reference content for the Typha component in Calico Enterprise that scales Felix connections to the Kubernetes API datastore. - [Reduce node impacts on datastore](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/overview): Reference overview of the Typha daemon in Calico Enterprise explaining how it reduces datastore load and scales Felix to large clusters. - [Configuring Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/configuration): Reference for Typha configuration parameters in Calico Enterprise covering environment variables and config file options for scaling the Kubernetes datastore. -- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus): Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics. +- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle): Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics. - [Configuration on public clouds](https://docs.tigera.io/calico-enterprise/latest/reference/public-cloud/): Public cloud reference for Calico Enterprise covering platform-specific networking notes for AWS, Azure, and GCE deployments. - [Amazon Web Services](https://docs.tigera.io/calico-enterprise/latest/reference/public-cloud/aws): Reference for running Calico Enterprise on Amazon Web Services covering supported networking modes and AWS platform integration notes. - [Azure](https://docs.tigera.io/calico-enterprise/latest/reference/public-cloud/azure): Reference for running Calico Enterprise on Microsoft Azure covering supported networking modes and user-defined routes. diff --git a/static/calico/3.25/licenses/third-party-attributions.html b/static/calico/3.25/licenses/third-party-attributions.html index 50263db0a0..48ac14ed9c 100644 --- a/static/calico/3.25/licenses/third-party-attributions.html +++ b/static/calico/3.25/licenses/third-party-attributions.html @@ -8760,7 +8760,7 @@

    Package Info

    - client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/prometheus/client_golang + client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/pickle/client_golang
    @@ -9214,7 +9214,7 @@

    Package Info

    - client_model (63fb9822ca3ba7a4ba5184071fb8f2ea000a99ef) git+github.com/prometheus/client_model + client_model (63fb9822ca3ba7a4ba5184071fb8f2ea000a99ef) git+github.com/pickle/client_model
    @@ -11272,7 +11272,7 @@

    Package Info

    - common (0ec6a33fff8b8a6950b82f03c4bfabaf61ac4813) git+github.com/prometheus/common + common (0ec6a33fff8b8a6950b82f03c4bfabaf61ac4813) git+github.com/pickle/common
    @@ -32883,8 +32883,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle
    @@ -58956,7 +58956,7 @@

    Package Info

    - procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/prometheus/procfs + procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/pickle/procfs
    diff --git a/static/calico/3.26/licenses/index.html b/static/calico/3.26/licenses/index.html index f06134159c..fc0fb2c70b 100644 --- a/static/calico/3.26/licenses/index.html +++ b/static/calico/3.26/licenses/index.html @@ -5290,7 +5290,7 @@

    Package Info

    - client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/prometheus/client_golang + client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/pickle/client_golang
    @@ -5744,7 +5744,7 @@

    Package Info

    - client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/prometheus/client_model + client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/pickle/client_model
    @@ -7802,7 +7802,7 @@

    Package Info

    - common (49b36038aead362ce78f09337dc5872000bd048a) git+github.com/prometheus/common + common (49b36038aead362ce78f09337dc5872000bd048a) git+github.com/pickle/common
    @@ -29054,8 +29054,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle
    @@ -56700,7 +56700,7 @@

    Package Info

    - procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/prometheus/procfs + procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/pickle/procfs
    diff --git a/static/calico/3.27/licenses/third-party-attributions.html b/static/calico/3.27/licenses/third-party-attributions.html index 2498ec3038..88836fc6ab 100644 --- a/static/calico/3.27/licenses/third-party-attributions.html +++ b/static/calico/3.27/licenses/third-party-attributions.html @@ -11298,7 +11298,7 @@

    Package Info

    - client_golang (3583c1e1d085b75cab406c78b015562d45552b39) git+github.com/prometheus/client_golang + client_golang (3583c1e1d085b75cab406c78b015562d45552b39) git+github.com/pickle/client_golang
    @@ -11821,7 +11821,7 @@

    Package Info

    Authors: bwplotka@gmail.com, arthur.sens@coralogix.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, superq@gmail.com, 49699333+dependabot[bot]@users.noreply.github.com, arthursens2005@gmail.com, @@ -11972,7 +11972,7 @@

    Package Info

    seth.bunce@gmail.com, 86919550+lukasauk@users.noreply.github.com -
  • Package Download URL: https://github.com/prometheus/client_golang/archive/3583c1e1d085b75cab406c78b015562d45552b39.zip
    • +
  • Package Download URL: https://github.com/pickle/client_golang/archive/3583c1e1d085b75cab406c78b015562d45552b39.zip
  • File Path(s): go.mod
    • @@ -11980,7 +11980,7 @@

    Package Info

    - client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/prometheus/client_model + client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/pickle/client_model
    @@ -12431,7 +12431,7 @@

    Package Info

  • Authors: beorn@grafana.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, 49699333+dependabot[bot]@users.noreply.github.com, superq@gmail.com, zhaoziqi9146@gmail.com, @@ -12446,7 +12446,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com
    • -
  • Package Download URL: https://github.com/prometheus/client_model/archive/91c3945f2cfbfb9040e34a0b6764d804b5a5a490.zip
    • +
  • Package Download URL: https://github.com/pickle/client_model/archive/91c3945f2cfbfb9040e34a0b6764d804b5a5a490.zip
  • File Path(s): go.mod
    • @@ -15121,7 +15121,7 @@

    Package Info

    - common (94bf9828e56d9670579b28a9f78237d3cd8d0395) git+github.com/prometheus/common + common (94bf9828e56d9670579b28a9f78237d3cd8d0395) git+github.com/pickle/common
    @@ -15683,7 +15683,7 @@

    Package Info

    dstdfx@gmail.com, abursavich@gmail.com, jbampton@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, pasquier.simon@gmail.com, cyril.tovena@gmail.com, bknecht@protonmail.ch, @@ -15756,7 +15756,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@prometheus.io, + matthias@pickle.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -15765,7 +15765,7 @@

    Package Info

    38865967+wasim-nihal@users.noreply.github.com, arianna.vespri@yahoo.it -
  • Package Download URL: https://github.com/prometheus/common/archive/94bf9828e56d9670579b28a9f78237d3cd8d0395.zip
    • +
  • Package Download URL: https://github.com/pickle/common/archive/94bf9828e56d9670579b28a9f78237d3cd8d0395.zip
  • File Path(s): go.mod
    • @@ -47235,8 +47235,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle
    @@ -47707,7 +47707,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -88763,7 +88763,7 @@

    Package Info

    - procfs (332e865adfebaa7eaedc94535a3f12f7e5eeb2d4) git+github.com/prometheus/procfs + procfs (332e865adfebaa7eaedc94535a3f12f7e5eeb2d4) git+github.com/pickle/procfs
    @@ -89225,7 +89225,7 @@

    Package Info

    superq@gmail.com, 49479987+bo-er@users.noreply.github.com, binjip978@gmail.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, benjamin.drung@ionos.com, sergii@zasenko.name, kulakov.home@gmail.com, @@ -89321,7 +89321,7 @@

    Package Info

    mdlayher@gmail.com, mwasilewski@gmx.com -
  • Package Download URL: https://github.com/prometheus/procfs/archive/332e865adfebaa7eaedc94535a3f12f7e5eeb2d4.zip
    • +
  • Package Download URL: https://github.com/pickle/procfs/archive/332e865adfebaa7eaedc94535a3f12f7e5eeb2d4.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.28/licenses/third-party-attributions.html b/static/calico/3.28/licenses/third-party-attributions.html index 706f211d3c..869af50331 100644 --- a/static/calico/3.28/licenses/third-party-attributions.html +++ b/static/calico/3.28/licenses/third-party-attributions.html @@ -12440,7 +12440,7 @@

    Package Info

    - client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/prometheus/client_golang + client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/pickle/client_golang
    @@ -12963,7 +12963,7 @@

    Package Info

    Authors: bwplotka@gmail.com, arthur.sens@coralogix.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, superq@gmail.com, 49699333+dependabot[bot]@users.noreply.github.com, arthursens2005@gmail.com, @@ -13114,7 +13114,7 @@

    Package Info

    krajorama@users.noreply.github.com, gyorgy.krajcsovits@grafana.com -
  • Package Download URL: https://github.com/prometheus/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
    • +
  • Package Download URL: https://github.com/pickle/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
  • File Path(s): go.mod
    • @@ -13122,7 +13122,7 @@

    Package Info

    - client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/prometheus/client_model + client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/pickle/client_model
    @@ -13574,7 +13574,7 @@

    Package Info

    Authors: beorn@grafana.com, 49699333+dependabot[bot]@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, superq@gmail.com, zhaoziqi9146@gmail.com, arianna.vespri@yahoo.it, @@ -13588,7 +13588,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com -
  • Package Download URL: https://github.com/prometheus/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
    • +
  • Package Download URL: https://github.com/pickle/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
  • File Path(s): go.mod
    • @@ -15031,7 +15031,7 @@

    Package Info

    - common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/prometheus/common + common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/pickle/common
    @@ -15590,7 +15590,7 @@

    Package Info

    superq@gmail.com, owen.williams@grafana.com, 49699333+dependabot[bot]@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, mail@jkroepke.de, 33664289+tjhop@users.noreply.github.com, matthieu.morel35@gmail.com, @@ -15669,7 +15669,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@prometheus.io, + matthias@pickle.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -15678,7 +15678,7 @@

    Package Info

    38865967+wasim-nihal@users.noreply.github.com, arianna.vespri@yahoo.it -
  • Package Download URL: https://github.com/prometheus/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
    • +
  • Package Download URL: https://github.com/pickle/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
  • File Path(s): go.mod
    • @@ -30912,8 +30912,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle
    @@ -31384,7 +31384,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -56950,7 +56950,7 @@

    Package Info

    - procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/prometheus/procfs + procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/pickle/procfs
    @@ -57412,7 +57412,7 @@

    Package Info

    superq@gmail.com, 49479987+bo-er@users.noreply.github.com, binjip978@gmail.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, benjamin.drung@ionos.com, sergii@zasenko.name, kulakov.home@gmail.com, @@ -57510,7 +57510,7 @@

    Package Info

    mwasilewski@gmx.com, mhutchinson@gmail.com -
  • Package Download URL: https://github.com/prometheus/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
    • +
  • Package Download URL: https://github.com/pickle/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.29/licenses/third-party-attributions.html b/static/calico/3.29/licenses/third-party-attributions.html index 6de8a6a601..0953a07169 100644 --- a/static/calico/3.29/licenses/third-party-attributions.html +++ b/static/calico/3.29/licenses/third-party-attributions.html @@ -12730,7 +12730,7 @@

    Package Info

    - client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/prometheus/client_golang + client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/pickle/client_golang

    @@ -13259,7 +13259,7 @@

    Package Info

    kakkoyun@users.noreply.github.com, saswataminsta@yahoo.com, 44365948+mahendrapaipuri@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, arthursens2005@gmail.com, dongjiang1989@126.com, 115284013+Saumya40-codes@users.noreply.github.com, @@ -13421,7 +13421,7 @@

    Package Info

    seth.bunce@gmail.com, 86919550+lukasauk@users.noreply.github.com -
  • Package Download URL: https://github.com/prometheus/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
    • +
  • Package Download URL: https://github.com/pickle/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
  • File Path(s): go.mod
    • @@ -13429,7 +13429,7 @@

    Package Info

    - client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/prometheus/client_model + client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/pickle/client_model

    @@ -13880,7 +13880,7 @@

    Package Info

  • Authors: beorn@grafana.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, 49699333+dependabot[bot]@users.noreply.github.com, superq@gmail.com, zhaoziqi9146@gmail.com, @@ -13894,7 +13894,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com
    • -
  • Package Download URL: https://github.com/prometheus/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
    • +
  • Package Download URL: https://github.com/pickle/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
  • File Path(s): go.mod
    • @@ -16082,7 +16082,7 @@

    Package Info

    - common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/prometheus/common + common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/pickle/common

    @@ -16639,7 +16639,7 @@

    Package Info

    harm@dds.nl, arve.knudsen@gmail.com, julius.hinze@grafana.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, 33664289+tjhop@users.noreply.github.com, 49699333+dependabot[bot]@users.noreply.github.com, bwplotka@gmail.com, @@ -16722,7 +16722,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@prometheus.io, + matthias@pickle.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -16734,7 +16734,7 @@

    Package Info

    t.hoplock@gmail.com, federico.torres@grafana.com -
  • Package Download URL: https://github.com/prometheus/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
    • +
  • Package Download URL: https://github.com/pickle/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
  • File Path(s): go.mod
    • @@ -36467,8 +36467,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle

    @@ -36939,7 +36939,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -70485,7 +70485,7 @@

    Package Info

    - procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/prometheus/procfs + procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/pickle/procfs

    @@ -70947,7 +70947,7 @@

    Package Info

    superq@gmail.com, 49479987+bo-er@users.noreply.github.com, binjip978@gmail.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, benjamin.drung@ionos.com, sergii@zasenko.name, kulakov.home@gmail.com, @@ -71053,7 +71053,7 @@

    Package Info

    mmichish@yahoo-corp.jp, weidong@uniontech.com -
  • Package Download URL: https://github.com/prometheus/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
    • +
  • Package Download URL: https://github.com/pickle/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.30/licenses/third-party-attributions.html b/static/calico/3.30/licenses/third-party-attributions.html index 065f79d75e..63ef031add 100644 --- a/static/calico/3.30/licenses/third-party-attributions.html +++ b/static/calico/3.30/licenses/third-party-attributions.html @@ -15107,7 +15107,7 @@

    Package Info

    - client_golang (8a42da3e4bfdc7ea408fcd886064dffc4daffb22) git+github.com/prometheus/client_golang + client_golang (8a42da3e4bfdc7ea408fcd886064dffc4daffb22) git+github.com/pickle/client_golang

    @@ -15711,7 +15711,7 @@

    Package Info

    beorn@grafana.com, jacksontj.89@gmail.com, carlpett@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, bjoern@rabenste.in, kgeorgie@redhat.com, yaozengzeng@foxmail.com, @@ -15900,7 +15900,7 @@

    Package Info

    86919550+lukasauk@users.noreply.github.com, ganeshvern@gmail.com -
  • Package Download URL: https://github.com/prometheus/client_golang/archive/8a42da3e4bfdc7ea408fcd886064dffc4daffb22.zip
    • +
  • Package Download URL: https://github.com/pickle/client_golang/archive/8a42da3e4bfdc7ea408fcd886064dffc4daffb22.zip
  • File Path(s): go.mod
    • @@ -15908,7 +15908,7 @@

    Package Info

    - client_model (571429e996ba2d9499e3dcb12926767ba953c0ef) git+github.com/prometheus/client_model + client_model (571429e996ba2d9499e3dcb12926767ba953c0ef) git+github.com/pickle/client_model

    @@ -16360,7 +16360,7 @@

    Package Info

    Authors: superq@gmail.com, beorn@grafana.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, zhaoziqi9146@gmail.com, matt.proud@gmail.com, 49699333+dependabot[bot]@users.noreply.github.com, @@ -16373,7 +16373,7 @@

    Package Info

    arianna.vespri@yahoo.it, arthur.sens@coralogix.com -
  • Package Download URL: https://github.com/prometheus/client_model/archive/571429e996ba2d9499e3dcb12926767ba953c0ef.zip
    • +
  • Package Download URL: https://github.com/pickle/client_model/archive/571429e996ba2d9499e3dcb12926767ba953c0ef.zip
  • File Path(s): go.mod
    • @@ -19089,7 +19089,7 @@

    Package Info

    - common (cf3c56f7b7d09d67cb46592c5e930651fd2d296e) git+github.com/prometheus/common + common (cf3c56f7b7d09d67cb46592c5e930651fd2d296e) git+github.com/pickle/common

    @@ -19539,7 +19539,7 @@

    Package Info

    @@ -47506,8 +47506,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle

    @@ -47978,7 +47978,7 @@

    Package Info

    spasquie@redhat.com, p.versockas@gmail.com -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -87903,7 +87903,7 @@

    Package Info

    - procfs (51919fd4b9d0aaca69854ac81bdeda5f96dab366) git+github.com/prometheus/procfs + procfs (51919fd4b9d0aaca69854ac81bdeda5f96dab366) git+github.com/pickle/procfs

    @@ -88365,7 +88365,7 @@

    Package Info

    wolandr@gmail.com, tklauser@distanz.ch, github@frittentheke.de, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, daniel.swarbrick@gmail.com, zhsj@debian.org, binjip978@gmail.com, @@ -88485,7 +88485,7 @@

    Package Info

    remuso@gmail.com, miliacristian4@gmail.com -
  • Package Download URL: https://github.com/prometheus/procfs/archive/51919fd4b9d0aaca69854ac81bdeda5f96dab366.zip
    • +
  • Package Download URL: https://github.com/pickle/procfs/archive/51919fd4b9d0aaca69854ac81bdeda5f96dab366.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.31/licenses/third-party-attributions.html b/static/calico/3.31/licenses/third-party-attributions.html index c5b56f599e..83d5213c17 100644 --- a/static/calico/3.31/licenses/third-party-attributions.html +++ b/static/calico/3.31/licenses/third-party-attributions.html @@ -19197,7 +19197,7 @@

    Package Info

    - client_golang (e4b2208dd8cb6d1425f00250db842ec3c1e8749e) git+github.com/prometheus/client_golang + client_golang (e4b2208dd8cb6d1425f00250db842ec3c1e8749e) git+github.com/pickle/client_golang

    @@ -19806,7 +19806,7 @@

    Package Info

    kakkoyun@users.noreply.github.com, saswataminsta@yahoo.com, 44365948+mahendrapaipuri@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, arthursens2005@gmail.com, dongjiang1989@126.com, 115284013+Saumya40-codes@users.noreply.github.com, @@ -19969,7 +19969,7 @@

    Package Info

    seth.bunce@gmail.com, 86919550+lukasauk@users.noreply.github.com -
  • Package Download URL: https://github.com/prometheus/client_golang/archive/e4b2208dd8cb6d1425f00250db842ec3c1e8749e.zip
    • +
  • Package Download URL: https://github.com/pickle/client_golang/archive/e4b2208dd8cb6d1425f00250db842ec3c1e8749e.zip
  • File Path(s): go.mod
    • @@ -19977,7 +19977,7 @@

    Package Info

    - client_model (eb136e513d419e0c31ad750922f0a6f7675c2dee) git+github.com/prometheus/client_model + client_model (eb136e513d419e0c31ad750922f0a6f7675c2dee) git+github.com/pickle/client_model

    @@ -20428,7 +20428,7 @@

    Package Info

  • Authors: beorn@grafana.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, 49699333+dependabot[bot]@users.noreply.github.com, superq@gmail.com, zhaoziqi9146@gmail.com, @@ -20442,7 +20442,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com
    • -
  • Package Download URL: https://github.com/prometheus/client_model/archive/eb136e513d419e0c31ad750922f0a6f7675c2dee.zip
    • +
  • Package Download URL: https://github.com/pickle/client_model/archive/eb136e513d419e0c31ad750922f0a6f7675c2dee.zip
  • File Path(s): go.mod
    • @@ -23013,7 +23013,7 @@

    Package Info

    - common (75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a) git+github.com/prometheus/common + common (75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a) git+github.com/pickle/common

    @@ -23484,7 +23484,7 @@

    Package Info

    harm@dds.nl, arve.knudsen@gmail.com, julius.hinze@grafana.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, 33664289+tjhop@users.noreply.github.com, 49699333+dependabot[bot]@users.noreply.github.com, bwplotka@gmail.com, @@ -23568,7 +23568,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@prometheus.io, + matthias@pickle.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -23580,7 +23580,7 @@

    Package Info

    t.hoplock@gmail.com, federico.torres@grafana.com -
  • Package Download URL: https://github.com/prometheus/common/archive/75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a.zip
    • +
  • Package Download URL: https://github.com/pickle/common/archive/75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a.zip
  • File Path(s): go.mod
    • @@ -56476,8 +56476,8 @@

    Package Info

    -
    - go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus +
    + go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle

    @@ -56948,7 +56948,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -97012,7 +97012,7 @@

    Package Info

    - procfs (61fe41207276bc95c4c391762e9ef137385e8a5d) git+github.com/prometheus/procfs + procfs (61fe41207276bc95c4c391762e9ef137385e8a5d) git+github.com/pickle/procfs

    @@ -97463,7 +97463,7 @@

    Package Info

  • Authors: 49699333+dependabot[bot]@users.noreply.github.com, - prometheus-team@googlegroups.com, + pickle-team@googlegroups.com, jj@asama.ai, superq@gmail.com, robbat2@orbis-terrarum.net, @@ -97580,15 +97580,15 @@

    Package Info

    mmichish@yahoo-corp.jp, weidong@uniontech.com
    • -
  • Package Download URL: https://github.com/prometheus/procfs/archive/61fe41207276bc95c4c391762e9ef137385e8a5d.zip
    • +
  • Package Download URL: https://github.com/pickle/procfs/archive/61fe41207276bc95c4c391762e9ef137385e8a5d.zip
  • File Path(s): go.mod
    • -
    - prometheus-operator (4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b) git+github.com/prometheus-operator/prometheus-operator +
    + pickle-operator (4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b) git+github.com/pickle-operator/pickle-operator

    @@ -98652,7 +98652,7 @@

    Package Info

    145814986+Whitea029@users.noreply.github.com, angelbarrerasanchez@gmail.com -
  • Package Download URL: https://github.com/prometheus-operator/prometheus-operator/archive/4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b.zip
    • +
  • Package Download URL: https://github.com/pickle-operator/pickle-operator/archive/4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b.zip
  • File Path(s): go.mod
    • @@ -145506,37 +145506,37 @@ 
    Copyright © 2021,2023-2024 Tigera, Inc. All rights reserved.
    Copyright © 2016 Microsoft Corporation
    - 
    Copyright © The prometheus-operator Authors
    + 
    Copyright © The pickle-operator Authors
    - 
    Copyright © 2016 The prometheus-operator Authors
    + 
    Copyright © 2016 The pickle-operator Authors
    - 
    Copyright © 2021 The prometheus-operator Authors
    + 
    Copyright © 2021 The pickle-operator Authors
    - 
    Copyright ©  The prometheus-operator Authors
    + 
    Copyright ©  The pickle-operator Authors
    - 
    Copyright © 2024 The prometheus-operator Authors
    + 
    Copyright © 2024 The pickle-operator Authors
    - 
    Copyright © 2019 The prometheus-operator Authors
    + 
    Copyright © 2019 The pickle-operator Authors
    - 
    Copyright © 2020 The prometheus-operator Authors
    + 
    Copyright © 2020 The pickle-operator Authors
    - 
    Copyright © 2018 The prometheus-operator Authors
    + 
    Copyright © 2018 The pickle-operator Authors
    - 
    Copyright © 2017 The prometheus-operator Authors
    + 
    Copyright © 2017 The pickle-operator Authors
    - 
    Copyright © 2023 The prometheus-operator Authors
    + 
    Copyright © 2023 The pickle-operator Authors
    - 
    Copyright © 2022 The prometheus-operator Authors
    + 
    Copyright © 2022 The pickle-operator Authors
    Copyright © 2017 Unknwon
    diff --git a/static/calico/3.32/licenses/third-party-attributions.html b/static/calico/3.32/licenses/third-party-attributions.html index d283f64141..b4ee0c0d0b 100644 --- a/static/calico/3.32/licenses/third-party-attributions.html +++ b/static/calico/3.32/licenses/third-party-attributions.html @@ -44809,8 +44809,8 @@

    Package Info

    -
    - github.com/grpc-ecosystem/go-grpc-prometheus (v1.2.0) go+github.com/grpc-ecosystem/go-grpc-prometheus +
    + github.com/grpc-ecosystem/go-grpc-pickle (v1.2.0) go+github.com/grpc-ecosystem/go-grpc-pickle

    @@ -44939,7 +44939,7 @@

    Package Info

    bclermont, AlekSi -
  • Package Download URL: https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-prometheus/@v/v1.2.0.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-pickle/@v/v1.2.0.zip
  • File Path(s): go.mod
    • @@ -52653,8 +52653,8 @@

    Package Info

    -
    - github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring (v0.80.1) go+github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring +
    + github.com/pickle-operator/pickle-operator/pkg/apis/monitoring (v0.80.1) go+github.com/pickle-operator/pickle-operator/pkg/apis/monitoring

    @@ -52669,7 +52669,7 @@ 

    -    Copyright 2018 The prometheus-operator Authors
+    Copyright 2018 The pickle-operator Authors
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
@@ -53117,15 +53117,15 @@ 
    Package Info
    
                       apgapg, 
                       artpdr
                   
-                                
  • Package Download URL: https://proxy.golang.org/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/@v/v0.80.1.zip
    • 
+                                
  • Package Download URL: https://proxy.golang.org/github.com/pickle-operator/pickle-operator/pkg/apis/monitoring/@v/v0.80.1.zip
    • 
                                   
  • File Path(s): go.mod
    •
    -
    - github.com/prometheus/client_golang (v1.23.2) go+github.com/prometheus/client_golang +
    + github.com/pickle/client_golang (v1.23.2) go+github.com/pickle/client_golang
    @@ -53609,15 +53609,15 @@

    Package Info

    jeffwidman, jimmidyson -
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/client_golang/@v/v1.23.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/pickle/client_golang/@v/v1.23.2.zip
  • File Path(s): go.mod
    • -
    - github.com/prometheus/client_model (v0.6.2) go+github.com/prometheus/client_model +
    + github.com/pickle/client_model (v0.6.2) go+github.com/pickle/client_model

    @@ -53742,15 +53742,15 @@

    Package Info

    bufdev, juliusv -
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/client_model/@v/v0.6.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/pickle/client_model/@v/v0.6.2.zip
  • File Path(s): go.mod
    • -
    - github.com/prometheus/common (v0.67.2) go+github.com/prometheus/common +
    + github.com/pickle/common (v0.67.2) go+github.com/pickle/common

    @@ -53975,15 +53975,15 @@

    Package Info

    FUSAKLA, mattkanwisher -
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/common/@v/v0.67.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/pickle/common/@v/v0.67.2.zip
  • File Path(s): go.mod
    • -
    - github.com/prometheus/procfs (v0.19.2) go+github.com/prometheus/procfs +
    + github.com/pickle/procfs (v0.19.2) go+github.com/pickle/procfs

    @@ -54271,7 +54271,7 @@

    Package Info

    felixonmars, flixr -
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/procfs/@v/v0.19.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/pickle/procfs/@v/v0.19.2.zip
  • File Path(s): go.mod
    • @@ -111885,7 +111885,7 @@ 
    Copyright © 2014-2021 Docker Inc.
    Copyright © 2016-2017 The New York Times Company
    - 
    Copyright © 2018 The prometheus-operator Authors
    + 
    Copyright © 2018 The pickle-operator Authors
    Copyright © 2014 Steve Francia <spf@spf13.com>.
    diff --git a/static/calico/llms-full.txt b/static/calico/llms-full.txt index e9d817c886..f2d0186d30 100644 --- a/static/calico/llms-full.txt +++ b/static/calico/llms-full.txt @@ -20485,7 +20485,7 @@ In Calico, we program these LUTs to the eBPF data plane as maps which can grow u ## Additional resources[​](#additional-resources) -- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico/latest/reference/felix/prometheus#load-balancer-metrics) +- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico/latest/reference/felix/pickle#load-balancer-metrics) - [FelixConfiguration](https://docs.tigera.io/calico/latest/reference/resources/felixconfig) - [Enable the eBPF data plane](https://docs.tigera.io/calico/latest/operations/ebpf/enabling-ebpf) - [Advertise Service IPs with BGP](https://docs.tigera.io/calico/latest/networking/configuring/advertise-service-ips) @@ -33608,9 +33608,9 @@ This example shows how to limit access to the calico/node Prometheus metrics end 4. Create a network policy that restricts access to the calico/node Prometheus metrics port. - Now let's create a network policy that limits access to the Prometheus metrics port such that only endpoints with the label `calico-prometheus-access: true` can access the metrics. + Now let's create a network policy that limits access to the Prometheus metrics port such that only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -33623,7 +33623,7 @@ This example shows how to limit access to the calico/node Prometheus metrics end metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: @@ -33649,7 +33649,7 @@ This example shows how to limit access to the calico/node Prometheus metrics end source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: @@ -33658,22 +33658,22 @@ This example shows how to limit access to the calico/node Prometheus metrics end - 9091 ``` - This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-prometheus-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to Calico. + This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. The ingress rule denies traffic to port 9091 unless the source of traffic has the label `calico-pickle-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to Calico. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 5. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach Calico's Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. + At this point, only endpoints that have the label `calico-pickle-access: true` can reach Calico's Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP network, you can create a [global network set](https://docs.tigera.io/calico/latest/reference/resources/globalnetworkset) using `calicoctl`. @@ -33687,11 +33687,11 @@ This example shows how to limit access to the calico/node Prometheus metrics end metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: @@ -33706,7 +33706,7 @@ This example shows how to limit access to the calico/node Prometheus metrics end If your Calico installation uses the Kubernetes API datastore and has greater than 50 nodes, it is likely that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml # Allow traffic to Prometheus only from sources that are @@ -33719,7 +33719,7 @@ kind: GlobalNetworkPolicy metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: @@ -33745,7 +33745,7 @@ spec: source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: @@ -33754,19 +33754,19 @@ spec: - 9093 ``` -This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-prometheus-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to Calico. +This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress deny rule. The ingress rule denies traffic to port 9093 unless the source of traffic has the label `calico-pickle-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that do not have the label, as well as any other network endpoints unknown to Calico. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers[​](#example-for-kube-controllers) If your Calico installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 @@ -33775,7 +33775,7 @@ kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system @@ -33803,7 +33803,7 @@ spec: source: - notSelector: calico-prometheus-access == "true" + notSelector: calico-pickle-access == "true" destination: @@ -33817,7 +33817,7 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ## Using an allow-list approach[​](#using-an-allow-list-approach) @@ -33914,9 +33914,9 @@ The basic process is as follows: 3. Create a network policy that allows access to the calico/node Prometheus metrics port. - Now let's create a network policy that allows access to the Prometheus metrics port such that only endpoints with the label `calico-prometheus-access: true` can access the metrics. + Now let's create a network policy that allows access to the Prometheus metrics port such that only endpoints with the label `calico-pickle-access: true` can access the metrics. - To do this, create a file named `calico-prometheus-policy.yaml` with the following contents. + To do this, create a file named `calico-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 @@ -33925,7 +33925,7 @@ The basic process is as follows: metadata: - name: restrict-calico-node-prometheus + name: restrict-calico-node-pickle spec: @@ -33949,7 +33949,7 @@ The basic process is as follows: source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: @@ -33958,22 +33958,22 @@ The basic process is as follows: - 9091 ``` - This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. The ingress rule allows traffic to port 9091 from any source with the label `calico-prometheus-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that have the label will be allowed access. + This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. The ingress rule allows traffic to port 9091 from any source with the label `calico-pickle-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash - calicoctl apply -f calico-prometheus-policy.yaml + calicoctl apply -f calico-pickle-policy.yaml ``` 4. Apply labels to any endpoints that should have access to the metrics. - At this point, only endpoints that have the label `calico-prometheus-access: true` can reach Calico's Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. + At this point, only endpoints that have the label `calico-pickle-access: true` can reach Calico's Prometheus metrics endpoints on each node. To grant access, simply add this label to the desired endpoints. For example, to allow access to a Kubernetes pod you can run the following command. ```bash - kubectl label pod my-prometheus-pod calico-prometheus-access=true + kubectl label pod my-pickle-pod calico-pickle-access=true ``` If you would like to grant access to a specific IP address in your network, you can create a [global network set](https://docs.tigera.io/calico/latest/reference/resources/globalnetworkset) using `calicoctl`. @@ -33987,11 +33987,11 @@ The basic process is as follows: metadata: - name: calico-prometheus-set + name: calico-pickle-set labels: - calico-prometheus-access: 'true' + calico-pickle-access: 'true' spec: @@ -34004,7 +34004,7 @@ The basic process is as follows: If your Calico installation uses the Kubernetes API datastore and has greater than 50 nodes, it is likely that you have installed Typha. This section shows how to use an additional network policy to secure the Typha Prometheus endpoints. -After following the steps above, create a file named `typha-prometheus-policy.yaml` with the following contents. +After following the steps above, create a file named `typha-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 @@ -34013,7 +34013,7 @@ kind: GlobalNetworkPolicy metadata: - name: restrict-typha-prometheus + name: restrict-typha-pickle spec: @@ -34035,7 +34035,7 @@ spec: source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: @@ -34044,19 +34044,19 @@ spec: - 9093 ``` -This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. The ingress rule allows traffic to port 9093 from any source with the label `calico-prometheus-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that have the label will be allowed access. +This policy selects all endpoints that have the label `running-calico: true`, and enforces a single ingress allow rule. The ingress rule allows traffic to port 9093 from any source with the label `calico-pickle-access: true`, meaning all Calico workload endpoints, host endpoints, and global network sets that have the label will be allowed access. Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f typha-prometheus-policy.yaml +calicoctl apply -f typha-pickle-policy.yaml ``` ### Example for kube-controllers[​](#example-for-kube-controllers-1) If your Calico installation exposes metrics from kube-controllers, you can limit access to those metrics with the following network policy. -Create a file named `kube-controllers-prometheus-policy.yaml` with the following contents. +Create a file named `kube-controllers-pickle-policy.yaml` with the following contents. ```yaml apiVersion: projectcalico.org/v3 @@ -34065,7 +34065,7 @@ kind: NetworkPolicy metadata: - name: restrict-kube-controllers-prometheus + name: restrict-kube-controllers-pickle namespace: calico-system @@ -34087,7 +34087,7 @@ spec: source: - selector: calico-prometheus-access == "true" + selector: calico-pickle-access == "true" destination: @@ -34099,7 +34099,7 @@ spec: Then, use `calicoctl` to apply this policy. ```bash -calicoctl apply -f kube-controllers-prometheus-policy.yaml +calicoctl apply -f kube-controllers-pickle-policy.yaml ``` ### Secure BGP sessions @@ -36707,7 +36707,7 @@ Using the open-source Prometheus monitoring and alerting toolkit, you can view t ## Concepts[​](#concepts) -### About Prometheus[​](#about-prometheus) +### About Prometheus[​](#about-pickle) The Prometheus monitoring tool scrapes metrics from instrumented jobs and displays time series data in a visualizer (such as Grafana). For Calico, the “jobs” that Prometheus can harvest metrics from are the Felix and Typha components. @@ -36752,7 +36752,7 @@ This tutorial will go through the necessary steps to implement basic monitoring #### **Felix configuration**[​](#felix-configuration) -Felix prometheus metrics are **disabled** by default. +Felix pickle metrics are **disabled** by default. > **SECONDARY:** A comprehensive list of configuration values can be [found at this link](https://docs.tigera.io/calico/latest/reference/felix/configuration). @@ -36763,7 +36763,7 @@ Use the following command to enable Felix metrics. **Tab: kubectl** ```bash -kubectl patch felixconfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": true}}' +kubectl patch felixconfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -36775,7 +36775,7 @@ felixconfiguration.projectcalico.org/default patched **Tab: calicoctl** ```bash -calicoctl patch felixconfiguration default --patch '{"spec":{"prometheusMetricsEnabled": true}}' +calicoctl patch felixconfiguration default --patch '{"spec":{"pickleMetricsEnabled": true}}' ``` You should see an output like below: @@ -37085,13 +37085,13 @@ EOF **Tab: kubectl** ```bash -kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"prometheusMetricsPort": 9095}}' +kubectl patch kubecontrollersconfiguration default --type=merge --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` **Tab: calicoctl** ```bash -calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"prometheusMetricsPort": 9095}}' +calicoctl patch kubecontrollersconfiguration default --patch '{"spec":{"pickleMetricsPort": 9095}}' ``` @@ -37139,7 +37139,7 @@ kind: ClusterRole metadata: - name: calico-prometheus-user + name: calico-pickle-user rules: @@ -37167,7 +37167,7 @@ kind: ServiceAccount metadata: - name: calico-prometheus-user + name: calico-pickle-user namespace: calico-monitoring @@ -37179,7 +37179,7 @@ kind: ClusterRoleBinding metadata: - name: calico-prometheus-user + name: calico-pickle-user roleRef: @@ -37187,26 +37187,26 @@ roleRef: kind: ClusterRole - name: calico-prometheus-user + name: calico-pickle-user subjects: - kind: ServiceAccount - name: calico-prometheus-user + name: calico-pickle-user namespace: calico-monitoring EOF ``` -### 3. Install prometheus[​](#3-install-prometheus) +### 3. Install pickle[​](#3-install-pickle) -#### **Create prometheus config file**[​](#create-prometheus-config-file) +#### **Create pickle config file**[​](#create-pickle-config-file) We can configure Prometheus using a ConfigMap to persistently store the desired settings. -> **SECONDARY:** A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). +> **SECONDARY:** A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). @@ -37221,13 +37221,13 @@ kind: ConfigMap metadata: - name: prometheus-config + name: pickle-config namespace: calico-monitoring data: - prometheus.yml: |- + pickle.yml: |- global: @@ -37239,7 +37239,7 @@ data: scrape_configs: - - job_name: 'prometheus' + - job_name: 'pickle' scrape_interval: 5s @@ -37347,13 +37347,13 @@ kind: ConfigMap metadata: - name: prometheus-config + name: pickle-config namespace: calico-monitoring data: - prometheus.yml: |- + pickle.yml: |- global: @@ -37365,7 +37365,7 @@ data: scrape_configs: - - job_name: 'prometheus' + - job_name: 'pickle' scrape_interval: 5s @@ -37458,7 +37458,7 @@ EOF -#### **Create Prometheus pod**[​](#create-prometheus-pod) +#### **Create Prometheus pod**[​](#create-pickle-pod) Now that you have a `serviceaccount` with permissions to gather metrics and have a valid config file for your Prometheus, it's time to create the Prometheus pod. @@ -37471,13 +37471,13 @@ kind: Pod metadata: - name: prometheus-pod + name: pickle-pod namespace: calico-monitoring labels: - app: prometheus-pod + app: pickle-pod role: monitoring @@ -37487,13 +37487,13 @@ spec: kubernetes.io/os: linux - serviceAccountName: calico-prometheus-user + serviceAccountName: calico-pickle-user containers: - - name: prometheus-pod + - name: pickle-pod - image: prom/prometheus + image: prom/pickle resources: @@ -37507,9 +37507,9 @@ spec: - name: config-volume - mountPath: /etc/prometheus/prometheus.yml + mountPath: /etc/pickle/pickle.yml - subPath: prometheus.yml + subPath: pickle.yml ports: @@ -37521,15 +37521,15 @@ spec: configMap: - name: prometheus-config + name: pickle-config EOF ``` -Check your cluster pods to assure pod creation was successful and prometheus pod is `Running`. +Check your cluster pods to assure pod creation was successful and pickle pod is `Running`. ```bash -kubectl get pods prometheus-pod -n calico-monitoring +kubectl get pods pickle-pod -n calico-monitoring ``` It should return something like the following. @@ -37537,20 +37537,20 @@ It should return something like the following. ```text NAME READY STATUS RESTARTS AGE -prometheus-pod 1/1 Running 0 16s +pickle-pod 1/1 Running 0 16s ``` ### 4. View metrics[​](#4-view-metrics) -You can access prometheus dashboard by using port-forwarding feature. +You can access pickle dashboard by using port-forwarding feature. ```bash -kubectl port-forward pod/prometheus-pod 9090:9090 -n calico-monitoring +kubectl port-forward pod/pickle-pod 9090:9090 -n calico-monitoring ``` -Browse to [http://localhost:9090](http://localhost:9090) you should be able to see prometheus dashboard. Type **felix\_active\_local\_endpoints** in the Expression input textbox then hit the execute button. Console table should be populated with all your nodes and quantity of endpoints in each of them. +Browse to [http://localhost:9090](http://localhost:9090) you should be able to see pickle dashboard. Type **felix\_active\_local\_endpoints** in the Expression input textbox then hit the execute button. Console table should be populated with all your nodes and quantity of endpoints in each of them. -> **SECONDARY:** A list of Felix metrics can be [found at this link](https://docs.tigera.io/calico/latest/reference/felix/prometheus). Similar lists can be found for [kube-controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus) and [Typha](https://docs.tigera.io/calico/latest/reference/typha/prometheus). +> **SECONDARY:** A list of Felix metrics can be [found at this link](https://docs.tigera.io/calico/latest/reference/felix/pickle). Similar lists can be found for [kube-controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle) and [Typha](https://docs.tigera.io/calico/latest/reference/typha/pickle). Push the `Add Graph` button, You should be able to see the metric plotted on a Graph. @@ -37593,7 +37593,7 @@ Return Calico configurations to their default state. **Tab: kubectl** ```bash -kubectl patch felixConfiguration default --type merge --patch '{"spec":{"prometheusMetricsEnabled": false}}' +kubectl patch felixConfiguration default --type merge --patch '{"spec":{"pickleMetricsEnabled": false}}' kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/spec/typhaMetricsPort"}]' ``` @@ -37601,7 +37601,7 @@ kubectl patch installation default --type=json -p '[{"op": "remove", "path":"/sp **Tab: calicoctl** ```bash -calicoctl patch felixConfiguration default --patch '{"spec":{"prometheusMetricsEnabled": false}}' +calicoctl patch felixConfiguration default --patch '{"spec":{"pickleMetricsEnabled": false}}' ``` @@ -37611,9 +37611,9 @@ Finally, remove the namespace and RBAC permissions. ```bash kubectl delete namespace calico-monitoring -kubectl delete ClusterRole calico-prometheus-user +kubectl delete ClusterRole calico-pickle-user -kubectl delete clusterrolebinding calico-prometheus-user +kubectl delete clusterrolebinding calico-pickle-user ``` ## Best practices[​](#best-practices) @@ -37644,7 +37644,7 @@ Using Grafana can be beneficial by providing a means to visualize metrics throug Grafana is an open source visualization and analytics tool that allows you to query, visualize, alert on, and explore metrics from a variety of data source, including Calico component metrics stored in Prometheus. -### About Prometheus[​](#about-prometheus) +### About Prometheus[​](#about-pickle) Prometheus is an open source monitoring tool that scrapes metrics from instrumented components and stores them as time series data which can then be visualized using tools such as Grafana. @@ -37659,9 +37659,9 @@ In this tutorial we assume you have This tutorial will go through the necessary steps to create Calico metrics dashboards with Grafana. -### Preparing Prometheus[​](#preparing-prometheus) +### Preparing Prometheus[​](#preparing-pickle) -Here you will create a service to make your prometheus visible to Grafana. +Here you will create a service to make your pickle visible to Grafana. ```bash kubectl apply -f - < **SECONDARY:** Guide with greater detail about Grafana datasources can be found [at this link](https://grafana.com/docs/grafana/latest/datasources/). -In this section you will use Grafana provisioning capabilities to create a prometheus datasource. +In this section you will use Grafana provisioning capabilities to create a pickle datasource. > **SECONDARY:** Guide with greater detail about provisioning can be found [at this link](https://grafana.com/docs/grafana/latest/administration/provisioning/). -Here You setup a datasource and pointing it to the prometheus service in your cluster. +Here You setup a datasource and pointing it to the pickle service in your cluster. ```bash kubectl apply -f - <:string, values:string)* | (Optional) ControlPlaneNodeSelector is used to select control plane nodes on which to run Calico components. This is globally applied to all resources created by the operator excluding daemonsets. | | `controlPlaneTolerations` *[Toleration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#toleration-v1-core) array* | (Optional) ControlPlaneTolerations specify tolerations which are then globally applied to all resources created by the operator. | | `controlPlaneReplicas` *integer* | (Optional) ControlPlaneReplicas defines how many replicas of the control plane core components will be deployed. This field applies to all control plane components that support High Availability. Defaults to 2. | -| `nodeMetricsPort` *integer* | (Optional) NodeMetricsPort specifies which port calico/node serves prometheus metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then prometheus metrics may still be configured through FelixConfiguration. | -| `typhaMetricsPort` *integer* | (Optional) TyphaMetricsPort specifies which port calico/typha serves prometheus metrics on. By default, metrics are not enabled. | +| `nodeMetricsPort` *integer* | (Optional) NodeMetricsPort specifies which port calico/node serves pickle metrics on. By default, metrics are not enabled. If specified, this overrides any FelixConfiguration resources which may exist. If omitted, then pickle metrics may still be configured through FelixConfiguration. | +| `typhaMetricsPort` *integer* | (Optional) TyphaMetricsPort specifies which port calico/typha serves pickle metrics on. By default, metrics are not enabled. | | `flexVolumePath` *string* | (Optional) FlexVolumePath optionally specifies a custom path for FlexVolume. If not specified, FlexVolume will be enabled by default. If set to 'None', FlexVolume will be disabled. The default is based on the kubernetesProvider. | | `kubeletVolumePluginPath` *string* | (Optional) KubeletVolumePluginPath optionally specifies enablement of Calico CSI plugin. If not specified, CSI will be enabled by default. If set to 'None', CSI will be disabled. Default: /var/lib/kubelet | | `nodeUpdateStrategy` *[DaemonSetUpdateStrategy](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#daemonsetupdatestrategy-v1-apps)* | (Optional) NodeUpdateStrategy can be used to customize the desired update strategy, such as the MaxUnavailable field. | @@ -44884,15 +44884,15 @@ Collect logs for pod tigera-packetcapture-758ff8c7db-slmd7 Collect describe for pod tigera-packetcapture-758ff8c7db-slmd7 -Collecting detailed diags for namespace tigera-prometheus... +Collecting detailed diags for namespace tigera-pickle... -Collecting detailed diags for pod calico-prometheus-operator-78d9b7f47c-q2d9v in namespace tigera-prometheus on node ip-172-16-101-171.us-west-2.compute.internal... +Collecting detailed diags for pod calico-pickle-operator-78d9b7f47c-q2d9v in namespace tigera-pickle on node ip-172-16-101-171.us-west-2.compute.internal... -Collecting diags for pod: calico-prometheus-operator-78d9b7f47c-q2d9v +Collecting diags for pod: calico-pickle-operator-78d9b7f47c-q2d9v -Collect logs for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collect logs for pod calico-pickle-operator-78d9b7f47c-q2d9v -Collect describe for pod calico-prometheus-operator-78d9b7f47c-q2d9v +Collect describe for pod calico-pickle-operator-78d9b7f47c-q2d9v Collecting detailed diags for namespace tigera-skraper... @@ -48144,94 +48144,94 @@ At most one selector-scoped FelixConfiguration should match any given node. If m | Schema | One of: `Debug`, `Error`, `Fatal`, `Info`, `Trace`, `Warning`. | | Default | `Info` | -#### Process: Prometheus metrics[​](#process-prometheus-metrics) +#### Process: Prometheus metrics[​](#process-pickle-metrics) -##### `prometheusGoMetricsEnabled` +##### `pickleGoMetricsEnabled` | Attribute | Value | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Key | `prometheusGoMetricsEnabled` | +| Key | `pickleGoMetricsEnabled` | | Description | Disables Go runtime metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | -##### `prometheusMetricsCAFile` +##### `pickleMetricsCAFile` | Attribute | Value | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsCAFile` | +| Key | `pickleMetricsCAFile` | | Description | Defines the absolute path to the TLS CA certificate file used for securing the /metrics endpoint. This certificate must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsCertFile` +##### `pickleMetricsCertFile` | Attribute | Value | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Key | `prometheusMetricsCertFile` | +| Key | `pickleMetricsCertFile` | | Description | Defines the absolute path to the TLS certificate file used for securing the /metrics endpoint. This certificate must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsClientAuth` +##### `pickleMetricsClientAuth` | Attribute | Value | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsClientAuth` | +| Key | `pickleMetricsClientAuth` | | Description | Specifies the client authentication type for the /metrics endpoint. This determines how the server validates client certificates. Default is "RequireAndVerifyClientCert". | | Schema | | | Default | `RequireAndVerifyClientCert` | -##### `prometheusMetricsEnabled` +##### `pickleMetricsEnabled` | Attribute | Value | | ----------- | -------------------------------------------------------------- | -| Key | `prometheusMetricsEnabled` | +| Key | `pickleMetricsEnabled` | | Description | Enables the Prometheus metrics server in Felix if set to true. | | Schema | Boolean. | | Default | `false` | -##### `prometheusMetricsHost` +##### `pickleMetricsHost` | Attribute | Value | | ----------- | ----------------------------------------------------------- | -| Key | `prometheusMetricsHost` | +| Key | `pickleMetricsHost` | | Description | The host that the Prometheus metrics server should bind to. | | Schema | String. | | Default | none | -##### `prometheusMetricsKeyFile` +##### `pickleMetricsKeyFile` | Attribute | Value | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusMetricsKeyFile` | +| Key | `pickleMetricsKeyFile` | | Description | Defines the absolute path to the private key file corresponding to the TLS certificate used for securing the /metrics endpoint. The private key must be valid and accessible by the calico-node process. | | Schema | String. | | Default | none | -##### `prometheusMetricsPort` +##### `pickleMetricsPort` | Attribute | Value | | ----------- | --------------------------------------------------------------- | -| Key | `prometheusMetricsPort` | +| Key | `pickleMetricsPort` | | Description | The TCP port that the Prometheus metrics server should bind to. | | Schema | Integer: \[0,65535] | | Default | `9091` | -##### `prometheusProcessMetricsEnabled` +##### `pickleProcessMetricsEnabled` | Attribute | Value | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusProcessMetricsEnabled` | +| Key | `pickleProcessMetricsEnabled` | | Description | Disables process metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | -##### `prometheusWireGuardMetricsEnabled` +##### `pickleWireGuardMetricsEnabled` | Attribute | Value | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Key | `prometheusWireGuardMetricsEnabled` | +| Key | `pickleWireGuardMetricsEnabled` | | Description | Disables wireguard metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. | | Schema | Boolean. | | Default | `true` | @@ -50585,7 +50585,7 @@ spec: etcdV3CompactionPeriod: 10m - prometheusMetricsPort: 9094 + pickleMetricsPort: 9094 controllers: @@ -50656,7 +50656,7 @@ spec: | ---------------------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------------------------- | ------- | | logSeverityScreen | The log severity above which logs are sent to the stdout. | Debug, Info, Warning, Error, Fatal | string | Info | | healthChecks | Enable support for health checks | Enabled, Disabled | string | Enabled | -| prometheusMetricsPort | Port on which to serve prometheus metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | +| pickleMetricsPort | Port on which to serve pickle metrics. | Set to 0 to disable, > 0 to enable. | TCP port | 9094 | | etcdV3CompactionPeriod | The period between etcdv3 compaction requests. Only applies when using etcd as the Calico datastore. | Set to 0 to disable, > 0 to enable | [Duration string](https://golang.org/pkg/time/#ParseDuration) | 10m | | controllers | Enabled controllers and their settings | | [Controllers](#controllers) | | @@ -53445,9 +53445,9 @@ kubectl get deployment.apps/calico-apiserver -n calico-system -o json | jq '.spe [Reference for Felix configuration parameters in Calico Open Source covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico/latest/reference/felix/configuration) -## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/prometheus) +## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/pickle) -[Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico/latest/reference/felix/prometheus) +[Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico/latest/reference/felix/pickle) ### Configuring Felix @@ -54321,7 +54321,7 @@ The full list of parameters which can be set is as follows. -### Process: Prometheus metrics[​](#process-prometheus-metrics) +### Process: Prometheus metrics[​](#process-pickle-metrics) #### `PrometheusGoMetricsEnabled` @@ -58500,9 +58500,9 @@ Total number of Maglev entries in conntrack table broken down by IP version, and [Reference for Typha configuration parameters in Calico Open Source covering environment variables and config file options for scaling the Kubernetes datastore.](https://docs.tigera.io/calico/latest/reference/typha/configuration) -## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/prometheus) +## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/pickle) -[Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico/latest/reference/typha/prometheus) +[Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico/latest/reference/typha/pickle) ### Typha overview @@ -59465,9 +59465,9 @@ For example: [Reference for kube-controllers configuration in Calico Open Source covering environment variables and KubeControllersConfiguration options.](https://docs.tigera.io/calico/latest/reference/kube-controllers/configuration) -## [📄️Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus) +## [📄️Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle) -[Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth.](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus) +[Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth.](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle) ### Configuring the Calico Kubernetes controllers @@ -61906,7 +61906,7 @@ This release adds support for Kubernetes 1.36. ## Other changes[​](#other-changes) -- Update bundled Istio version to 1.29.2, including CVE fixes for moby/spdystream, prometheus/prometheus, and opentelemetry-go/otel/sdk. [calico 12581](https://github.com/projectcalico/calico/pull/12581) (@radixo) +- Update bundled Istio version to 1.29.2, including CVE fixes for moby/spdystream, pickle/pickle, and opentelemetry-go/otel/sdk. [calico 12581](https://github.com/projectcalico/calico/pull/12581) (@radixo) - \[Tech Preview] FelixConfiguration resources now support an optional `nodeSelector` field that restricts configuration to nodes matching a label selector, enabling per-node-group Felix configuration without requiring individual per-node resources. At most one selector-scoped FelixConfiguration should match any given node; if multiple match, the oldest by creation time wins to avoid disrupting existing working configuration. Overlapping selectors are treated as a misconfiguration and this behavior may change in future releases. [calico 12497](https://github.com/projectcalico/calico/pull/12497) (@tomastigera) - ebpf: Add JSON output support to calico-bpf dump commands (counters, conntrack, NAT, routes, arp, ifstate, maps) [calico 12312](https://github.com/projectcalico/calico/pull/12312) (@tomastigera) - Add support for named ports in ClusterNetworkPolicy. [calico 12227](https://github.com/projectcalico/calico/pull/12227) (@mazdakn) diff --git a/static/calico/llms.txt b/static/calico/llms.txt index 403d5b41c5..19a3e96078 100644 --- a/static/calico/llms.txt +++ b/static/calico/llms.txt @@ -319,15 +319,15 @@ - [Configure resource requests and limits](https://docs.tigera.io/calico/latest/reference/configure-resources): Reference for setting Kubernetes resource requests and limits on Calico Open Source components managed by the Tigera Operator. - [Felix](https://docs.tigera.io/calico/latest/reference/felix/): Reference content for Felix in Calico Open Source, the per-node daemon that programs routes and policy rules into the Linux data plane. - [Configuring Felix](https://docs.tigera.io/calico/latest/reference/felix/configuration): Reference for Felix configuration parameters in Calico Open Source covering environment variables, FelixConfiguration fields, and per-node overrides. -- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/prometheus): Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation. +- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/pickle): Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation. - [Typha](https://docs.tigera.io/calico/latest/reference/typha/): Reference content for Typha in Calico Open Source, the fan-out daemon that scales Felix connections to the Kubernetes API datastore. - [Typha overview](https://docs.tigera.io/calico/latest/reference/typha/overview): Reference overview of the Typha daemon in Calico Open Source explaining how it reduces datastore load and scales Felix to large clusters. - [Configuring Typha](https://docs.tigera.io/calico/latest/reference/typha/configuration): Reference for Typha configuration parameters in Calico Open Source covering environment variables and config file options for scaling the Kubernetes datastore. -- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/prometheus): Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics. +- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/pickle): Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics. - [Configure the Calico CNI plugins](https://docs.tigera.io/calico/latest/reference/configure-cni-plugins): Reference for configuring the Calico Open Source CNI plugin and IPAM plugin through CNI network configuration files. - [kube-controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/): Reference content for the kube-controllers component in Calico Open Source that watches Kubernetes API events and reconciles cluster state. - [Configuring the Calico Kubernetes controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/configuration): Reference for kube-controllers configuration in Calico Open Source covering environment variables and KubeControllersConfiguration options. -- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus): Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth. +- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle): Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth. - [Configuration on public clouds](https://docs.tigera.io/calico/latest/reference/public-cloud/): Public cloud reference for Calico Open Source covering platform-specific networking notes for AWS, Azure, GCE, and IBM Cloud deployments. - [Amazon Web Services](https://docs.tigera.io/calico/latest/reference/public-cloud/aws): Reference for running Calico Open Source on Amazon Web Services covering supported networking modes, source/destination check requirements, and AWS-specific notes. - [Azure](https://docs.tigera.io/calico/latest/reference/public-cloud/azure): Reference for running Calico Open Source on Microsoft Azure covering supported networking modes, user-defined routes, and Azure platform notes. diff --git a/static/files/min-ui-user-rbac.yaml b/static/files/min-ui-user-rbac.yaml index 10662c8b5d..87cf5c972b 100644 --- a/static/files/min-ui-user-rbac.yaml +++ b/static/files/min-ui-user-rbac.yaml @@ -17,7 +17,7 @@ metadata: rules: - apiGroups: [""] resources: ["services/proxy"] - resourceNames: ["https:tigera-api:8080", "calico-node-prometheus:9090"] + resourceNames: ["https:tigera-api:8080", "calico-node-pickle:9090"] verbs: ["get","create"] # Access to flow logs, audit logs, and statistics - apiGroups: ["lma.tigera.io"] diff --git a/static/files/read-all-crud-default-rbac.yaml b/static/files/read-all-crud-default-rbac.yaml index b68674dd34..b3c4505b24 100644 --- a/static/files/read-all-crud-default-rbac.yaml +++ b/static/files/read-all-crud-default-rbac.yaml @@ -48,7 +48,7 @@ rules: # Access to allowed/denied packet stats and the license API. - apiGroups: [""] resources: ["services/proxy"] - resourceNames: ["https:tigera-api:8080", "calico-node-prometheus:9090"] + resourceNames: ["https:tigera-api:8080", "calico-node-pickle:9090"] verbs: ["get","create"] # Access to flow logs, audit logs, and statistics - apiGroups: ["lma.tigera.io"] diff --git a/static/json/calico-api-swagger.json b/static/json/calico-api-swagger.json index d439b16a0c..c2c26f2d31 100644 --- a/static/json/calico-api-swagger.json +++ b/static/json/calico-api-swagger.json @@ -1 +1 @@ -{"swagger":"2.0","info":{"title":"Generic API Server","version":"unversioned"},"paths":{"/apis/":{"get":{"description":"get available API versions","consumes":["application/json","application/yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["apis"],"operationId":"getAPIVersions","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIGroupList"}}}}},"/apis/projectcalico.org/":{"get":{"description":"get information of a group","consumes":["application/json","application/yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg"],"operationId":"getProjectcalicoOrgAPIGroup","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup"}}}}},"/apis/projectcalico.org/v3/":{"get":{"description":"get available resources","consumes":["application/json","application/yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"getProjectcalicoOrgV3APIResources","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList"}}}}},"/apis/projectcalico.org/v3/authenticationreviews":{"post":{"description":"create an AuthenticationReview","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3AuthenticationReview","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthenticationReview"}},"parameters":[{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/authorizationreviews":{"post":{"description":"create an AuthorizationReview","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3AuthorizationReview","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthorizationReview"}},"parameters":[{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgpconfigurations":{"get":{"description":"list or watch objects of kind BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3BGPConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"post":{"description":"create a BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"delete":{"description":"delete collection of BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionBGPConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgpconfigurations/{name}":{"get":{"description":"read the specified BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3BGPConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"put":{"description":"replace the specified BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"delete":{"description":"delete a BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"patch":{"description":"partially update the specified BGPConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the BGPConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgppeers":{"get":{"description":"list or watch objects of kind BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3BGPPeer","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeerList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"post":{"description":"create a BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"delete":{"description":"delete collection of BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionBGPPeer","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgppeers/{name}":{"get":{"description":"read the specified BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3BGPPeer","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"put":{"description":"replace the specified BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"delete":{"description":"delete a BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"patch":{"description":"partially update the specified BGPPeer","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the BGPPeer","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/clusterinformations":{"get":{"description":"list or watch objects of kind ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3ClusterInformation","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"post":{"description":"create a ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"delete":{"description":"delete collection of ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionClusterInformation","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/clusterinformations/{name}":{"get":{"description":"read the specified ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3ClusterInformation","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"put":{"description":"replace the specified ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"delete":{"description":"delete a ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"patch":{"description":"partially update the specified ClusterInformation","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the ClusterInformation","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/felixconfigurations":{"get":{"description":"list or watch objects of kind FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3FelixConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"post":{"description":"create a FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"delete":{"description":"delete collection of FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionFelixConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/felixconfigurations/{name}":{"get":{"description":"read the specified FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3FelixConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"put":{"description":"replace the specified FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"delete":{"description":"delete a FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"patch":{"description":"partially update the specified FelixConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the FelixConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerts":{"get":{"description":"list or watch objects of kind GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalAlert","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"post":{"description":"create a GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"delete":{"description":"delete collection of GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalAlert","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerts/{name}":{"get":{"description":"read the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalAlert","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"put":{"description":"replace the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"delete":{"description":"delete a GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"patch":{"description":"partially update the specified GlobalAlert","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalAlert","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerts/{name}/status":{"get":{"description":"read status of the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalAlertStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"put":{"description":"replace status of the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalAlertStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"patch":{"description":"partially update status of the specified GlobalAlert","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalAlertStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalAlert","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerttemplates":{"get":{"description":"list or watch objects of kind GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplateList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"post":{"description":"create a GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"delete":{"description":"delete collection of GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalAlertTemplate","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerttemplates/{name}":{"get":{"description":"read the specified GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"put":{"description":"replace the specified GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"delete":{"description":"delete a GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"patch":{"description":"partially update the specified GlobalAlertTemplate","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalAlertTemplate","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworkpolicies":{"get":{"description":"list or watch objects of kind GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"post":{"description":"create a GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"delete":{"description":"delete collection of GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworkpolicies/{name}":{"get":{"description":"read the specified GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"put":{"description":"replace the specified GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"delete":{"description":"delete a GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"patch":{"description":"partially update the specified GlobalNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworksets":{"get":{"description":"list or watch objects of kind GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSetList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"post":{"description":"create a GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"delete":{"description":"delete collection of GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworksets/{name}":{"get":{"description":"read the specified GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"put":{"description":"replace the specified GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"delete":{"description":"delete a GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"patch":{"description":"partially update the specified GlobalNetworkSet","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreports":{"get":{"description":"list or watch objects of kind GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalReport","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"post":{"description":"create a GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"delete":{"description":"delete collection of GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalReport","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreports/{name}":{"get":{"description":"read the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalReport","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"put":{"description":"replace the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"delete":{"description":"delete a GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"patch":{"description":"partially update the specified GlobalReport","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalReport","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreports/{name}/status":{"get":{"description":"read status of the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalReportStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"put":{"description":"replace status of the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalReportStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"patch":{"description":"partially update status of the specified GlobalReport","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalReportStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalReport","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreporttypes":{"get":{"description":"list or watch objects of kind GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalReportType","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportTypeList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"post":{"description":"create a GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"delete":{"description":"delete collection of GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalReportType","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreporttypes/{name}":{"get":{"description":"read the specified GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalReportType","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"put":{"description":"replace the specified GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"delete":{"description":"delete a GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"patch":{"description":"partially update the specified GlobalReportType","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalReportType","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalthreatfeeds":{"get":{"description":"list or watch objects of kind GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeedList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"post":{"description":"create a GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"delete":{"description":"delete collection of GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalThreatFeed","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalthreatfeeds/{name}":{"get":{"description":"read the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"put":{"description":"replace the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"delete":{"description":"delete a GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"patch":{"description":"partially update the specified GlobalThreatFeed","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalThreatFeed","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalthreatfeeds/{name}/status":{"get":{"description":"read status of the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalThreatFeedStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"put":{"description":"replace status of the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalThreatFeedStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"patch":{"description":"partially update status of the specified GlobalThreatFeed","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalThreatFeedStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalThreatFeed","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/hostendpoints":{"get":{"description":"list or watch objects of kind HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3HostEndpoint","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpointList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"post":{"description":"create a HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"delete":{"description":"delete collection of HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionHostEndpoint","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/hostendpoints/{name}":{"get":{"description":"read the specified HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3HostEndpoint","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"put":{"description":"replace the specified HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"delete":{"description":"delete a HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"patch":{"description":"partially update the specified HostEndpoint","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the HostEndpoint","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/ippools":{"get":{"description":"list or watch objects of kind IPPool","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3IPPool","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPoolList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"post":{"description":"create an IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"delete":{"description":"delete collection of IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionIPPool","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/ippools/{name}":{"get":{"description":"read the specified IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3IPPool","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"put":{"description":"replace the specified IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"delete":{"description":"delete an IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"patch":{"description":"partially update the specified IPPool","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the IPPool","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/kubecontrollersconfigurations":{"get":{"description":"list or watch objects of kind KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"post":{"description":"create a KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"delete":{"description":"delete collection of KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionKubeControllersConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/kubecontrollersconfigurations/{name}":{"get":{"description":"read the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"put":{"description":"replace the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"delete":{"description":"delete a KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"patch":{"description":"partially update the specified KubeControllersConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the KubeControllersConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/kubecontrollersconfigurations/{name}/status":{"get":{"description":"read status of the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3KubeControllersConfigurationStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"put":{"description":"replace status of the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3KubeControllersConfigurationStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"patch":{"description":"partially update status of the specified KubeControllersConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3KubeControllersConfigurationStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the KubeControllersConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/licensekeys":{"get":{"description":"list or watch objects of kind LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3LicenseKey","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKeyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"post":{"description":"create a LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"delete":{"description":"delete collection of LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionLicenseKey","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/licensekeys/{name}":{"get":{"description":"read the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3LicenseKey","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"put":{"description":"replace the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"delete":{"description":"delete a LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"patch":{"description":"partially update the specified LicenseKey","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the LicenseKey","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/licensekeys/{name}/status":{"get":{"description":"read status of the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3LicenseKeyStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"put":{"description":"replace status of the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3LicenseKeyStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"patch":{"description":"partially update status of the specified LicenseKey","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3LicenseKeyStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the LicenseKey","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/managedclusters":{"get":{"description":"list or watch objects of kind ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3ManagedCluster","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedClusterList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"post":{"description":"create a ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"delete":{"description":"delete collection of ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionManagedCluster","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/managedclusters/{name}":{"get":{"description":"read the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3ManagedCluster","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"put":{"description":"replace the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"delete":{"description":"delete a ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"patch":{"description":"partially update the specified ManagedCluster","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the ManagedCluster","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/managedclusters/{name}/status":{"get":{"description":"read status of the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3ManagedClusterStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"put":{"description":"replace status of the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3ManagedClusterStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"patch":{"description":"partially update status of the specified ManagedCluster","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3ManagedClusterStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the ManagedCluster","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networkpolicies":{"get":{"description":"list or watch objects of kind NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"post":{"description":"create a NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"delete":{"description":"delete collection of NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networkpolicies/{name}":{"get":{"description":"read the specified NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"put":{"description":"replace the specified NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"delete":{"description":"delete a NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"patch":{"description":"partially update the specified NetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the NetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networksets":{"get":{"description":"list or watch objects of kind NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSetList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"post":{"description":"create a NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"delete":{"description":"delete collection of NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networksets/{name}":{"get":{"description":"read the specified NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"put":{"description":"replace the specified NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"delete":{"description":"delete a NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"patch":{"description":"partially update the specified NetworkSet","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the NetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/packetcaptures":{"get":{"description":"list or watch objects of kind PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCaptureList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"post":{"description":"create a PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"delete":{"description":"delete collection of PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedPacketCapture","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/packetcaptures/{name}":{"get":{"description":"read the specified PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"put":{"description":"replace the specified PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"delete":{"description":"delete a PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"patch":{"description":"partially update the specified PacketCapture","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the PacketCapture","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagedkubernetesnetworkpolicies":{"get":{"description":"list or watch objects of kind StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"post":{"description":"create a StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"delete":{"description":"delete collection of StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagedkubernetesnetworkpolicies/{name}":{"get":{"description":"read the specified StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"put":{"description":"replace the specified StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"delete":{"description":"delete a StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"patch":{"description":"partially update the specified StagedKubernetesNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the StagedKubernetesNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagednetworkpolicies":{"get":{"description":"list or watch objects of kind StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"post":{"description":"create a StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"delete":{"description":"delete collection of StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagednetworkpolicies/{name}":{"get":{"description":"read the specified StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"put":{"description":"replace the specified StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"delete":{"description":"delete a StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"patch":{"description":"partially update the specified StagedNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the StagedNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/networkpolicies":{"get":{"description":"list or watch objects of kind NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NetworkPolicyForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/networksets":{"get":{"description":"list or watch objects of kind NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NetworkSetForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSetList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/packetcaptures":{"get":{"description":"list or watch objects of kind PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3PacketCaptureForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCaptureList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/profiles":{"get":{"description":"list or watch objects of kind Profile","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3Profile","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ProfileList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"post":{"description":"create a Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"delete":{"description":"delete collection of Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionProfile","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/profiles/{name}":{"get":{"description":"read the specified Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3Profile","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"put":{"description":"replace the specified Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"delete":{"description":"delete a Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"patch":{"description":"partially update the specified Profile","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the Profile","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/remoteclusterconfigurations":{"get":{"description":"list or watch objects of kind RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"post":{"description":"create a RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"delete":{"description":"delete collection of RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionRemoteClusterConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/remoteclusterconfigurations/{name}":{"get":{"description":"read the specified RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"put":{"description":"replace the specified RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"delete":{"description":"delete a RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"patch":{"description":"partially update the specified RemoteClusterConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the RemoteClusterConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/stagedglobalnetworkpolicies":{"get":{"description":"list or watch objects of kind StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"post":{"description":"create a StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"delete":{"description":"delete collection of StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionStagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/stagedglobalnetworkpolicies/{name}":{"get":{"description":"read the specified StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"put":{"description":"replace the specified StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"delete":{"description":"delete a StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"patch":{"description":"partially update the specified StagedGlobalNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the StagedGlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/stagedkubernetesnetworkpolicies":{"get":{"description":"list or watch objects of kind StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3StagedKubernetesNetworkPolicyForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/stagednetworkpolicies":{"get":{"description":"list or watch objects of kind StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3StagedNetworkPolicyForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/tiers":{"get":{"description":"list or watch objects of kind Tier","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3Tier","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.TierList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"post":{"description":"create a Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"delete":{"description":"delete collection of Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionTier","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/tiers/{name}":{"get":{"description":"read the specified Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3Tier","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"put":{"description":"replace the specified Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"delete":{"description":"delete a Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"patch":{"description":"partially update the specified Tier","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the Tier","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/watch/authenticationreviews/{name}":{"get":{"description":"watch changes to an object of kind AuthenticationReview. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3AuthenticationReview","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthenticationReview"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the AuthenticationReview","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/authorizationreviews/{name}":{"get":{"description":"watch changes to an object of kind AuthorizationReview. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3AuthorizationReview","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthorizationReview"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the AuthorizationReview","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgpconfigurations":{"get":{"description":"watch individual changes to a list of BGPConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgpconfigurations/{name}":{"get":{"description":"watch changes to an object of kind BGPConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the BGPConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgppeers":{"get":{"description":"watch individual changes to a list of BGPPeer. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPPeerList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgppeers/{name}":{"get":{"description":"watch changes to an object of kind BGPPeer. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPPeer","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the BGPPeer","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/clusterinformations":{"get":{"description":"watch individual changes to a list of ClusterInformation. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ClusterInformationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/clusterinformations/{name}":{"get":{"description":"watch changes to an object of kind ClusterInformation. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ClusterInformation","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the ClusterInformation","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/felixconfigurations":{"get":{"description":"watch individual changes to a list of FelixConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3FelixConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/felixconfigurations/{name}":{"get":{"description":"watch changes to an object of kind FelixConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3FelixConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the FelixConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerts":{"get":{"description":"watch individual changes to a list of GlobalAlert. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlertList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerts/{name}":{"get":{"description":"watch changes to an object of kind GlobalAlert. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlert","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalAlert","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerttemplates":{"get":{"description":"watch individual changes to a list of GlobalAlertTemplate. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlertTemplateList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerttemplates/{name}":{"get":{"description":"watch changes to an object of kind GlobalAlertTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlertTemplate","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalAlertTemplate","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworkpolicies":{"get":{"description":"watch individual changes to a list of GlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind GlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworksets":{"get":{"description":"watch individual changes to a list of GlobalNetworkSet. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkSetList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworksets/{name}":{"get":{"description":"watch changes to an object of kind GlobalNetworkSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkSet","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreports":{"get":{"description":"watch individual changes to a list of GlobalReport. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReportList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreports/{name}":{"get":{"description":"watch changes to an object of kind GlobalReport. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReport","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalReport","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreporttypes":{"get":{"description":"watch individual changes to a list of GlobalReportType. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReportTypeList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreporttypes/{name}":{"get":{"description":"watch changes to an object of kind GlobalReportType. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReportType","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalReportType","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalthreatfeeds":{"get":{"description":"watch individual changes to a list of GlobalThreatFeed. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalThreatFeedList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalthreatfeeds/{name}":{"get":{"description":"watch changes to an object of kind GlobalThreatFeed. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalThreatFeed","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalThreatFeed","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/hostendpoints":{"get":{"description":"watch individual changes to a list of HostEndpoint. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3HostEndpointList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/hostendpoints/{name}":{"get":{"description":"watch changes to an object of kind HostEndpoint. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3HostEndpoint","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the HostEndpoint","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/ippools":{"get":{"description":"watch individual changes to a list of IPPool. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3IPPoolList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/ippools/{name}":{"get":{"description":"watch changes to an object of kind IPPool. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3IPPool","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the IPPool","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/kubecontrollersconfigurations":{"get":{"description":"watch individual changes to a list of KubeControllersConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3KubeControllersConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/kubecontrollersconfigurations/{name}":{"get":{"description":"watch changes to an object of kind KubeControllersConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3KubeControllersConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the KubeControllersConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/licensekeys":{"get":{"description":"watch individual changes to a list of LicenseKey. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3LicenseKeyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/licensekeys/{name}":{"get":{"description":"watch changes to an object of kind LicenseKey. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3LicenseKey","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the LicenseKey","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/managedclusters":{"get":{"description":"watch individual changes to a list of ManagedCluster. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ManagedClusterList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/managedclusters/{name}":{"get":{"description":"watch changes to an object of kind ManagedCluster. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ManagedCluster","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the ManagedCluster","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networkpolicies":{"get":{"description":"watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networkpolicies/{name}":{"get":{"description":"watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the NetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networksets":{"get":{"description":"watch individual changes to a list of NetworkSet. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkSetList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networksets/{name}":{"get":{"description":"watch changes to an object of kind NetworkSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkSet","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the NetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/packetcaptures":{"get":{"description":"watch individual changes to a list of PacketCapture. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedPacketCaptureList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/packetcaptures/{name}":{"get":{"description":"watch changes to an object of kind PacketCapture. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedPacketCapture","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the PacketCapture","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagedkubernetesnetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedKubernetesNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagedkubernetesnetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind StagedKubernetesNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the StagedKubernetesNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagednetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagednetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind StagedNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the StagedNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/networkpolicies":{"get":{"description":"watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NetworkPolicyListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/networksets":{"get":{"description":"watch individual changes to a list of NetworkSet. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NetworkSetListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/packetcaptures":{"get":{"description":"watch individual changes to a list of PacketCapture. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3PacketCaptureListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/profiles":{"get":{"description":"watch individual changes to a list of Profile. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ProfileList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/profiles/{name}":{"get":{"description":"watch changes to an object of kind Profile. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3Profile","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the Profile","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/remoteclusterconfigurations":{"get":{"description":"watch individual changes to a list of RemoteClusterConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3RemoteClusterConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/remoteclusterconfigurations/{name}":{"get":{"description":"watch changes to an object of kind RemoteClusterConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3RemoteClusterConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the RemoteClusterConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagedglobalnetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedGlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedGlobalNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagedglobalnetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind StagedGlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedGlobalNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the StagedGlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagedkubernetesnetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedKubernetesNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedKubernetesNetworkPolicyListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagednetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedNetworkPolicyListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/tiers":{"get":{"description":"watch individual changes to a list of Tier. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3TierList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/tiers/{name}":{"get":{"description":"watch changes to an object of kind Tier. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3Tier","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the Tier","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/version/":{"get":{"description":"get the code version","consumes":["application/json"],"produces":["application/json"],"schemes":["https"],"tags":["version"],"operationId":"getCodeVersion","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.version.Info"}}}}}},"definitions":{"com.github.projectcalico.libcalico-go.lib.apis.v1.IPIPConfiguration":{"type":"object","properties":{"enabled":{"description":"When enabled is true, ipip tunneling will be used to deliver packets to destinations within this pool.","type":"boolean"},"mode":{"description":"The IPIP mode. This can be one of \"always\" or \"cross-subnet\". A mode of \"always\" will also use IPIP tunneling for routing to destination IP addresses within this pool. A mode of \"cross-subnet\" will only use IPIP tunneling when the destination node is on a different subnet to the originating node. The default value (if not specified) is \"always\".","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuditEventsSelection":{"description":"AuditEventsSelection defines which set of resources should be audited.","type":"object","properties":{"resources":{"description":"Resources lists the resources that will be included in the audit logs in the ReportData. Blank fields in the listed ResourceID structs are treated as wildcards.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuditResource"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuditResource":{"description":"AuditResource is used to filter Audit events in the Report configuration.\n\nAn empty field value indicates a wildcard. For example, if Resource is set to \"networkpolicies\" and all other fields are blank then this filter would include all NetworkPolicy resources across all namespaces, and would include both Calico and Kubernetes resource types.","type":"object","properties":{"apiGroup":{"description":"APIGroup is the name of the API group that contains the referred object (e.g. projectcalico.org).","type":"string"},"apiVersion":{"description":"APIVersion is the version of the API group that contains the referred object (e.g. v3).","type":"string"},"name":{"description":"The resource name.","type":"string"},"namespace":{"description":"The resource namespace.","type":"string"},"resource":{"description":"The resource type. The format is the lowercase plural as used in audit event selection and RBAC configuration.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthenticationReviewStatus":{"type":"object","properties":{"extra":{"type":"object","additionalProperties":{"type":"array","items":{"type":"string"}}},"groups":{"type":"array","items":{"type":"string"}},"name":{"type":"string"},"uid":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewResourceAttributes":{"type":"object","properties":{"apiGroup":{"description":"The API Group to check.","type":"string"},"resources":{"description":"The set of resources to check within the same API Group.","type":"array","items":{"type":"string"}},"verbs":{"description":"The set of verbs to check. This is expanded for each resource and within the same API Group.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewSpec":{"type":"object","properties":{"resourceAttributes":{"description":"The set of resource attributes that are being checked. Each resource attribute is expanded into individual kind/resource and verbs.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewResourceAttributes"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewStatus":{"type":"object","properties":{"authorizedResourceVerbs":{"description":"The set of authorized resource actions. A given API Group and resource combination will appear at most once in this slice.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerbs"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceGroup":{"type":"object","required":["namespace"],"properties":{"namespace":{"description":"The namespace. If this is empty then the user is authorized cluster-wide (i.e. across all namespaces). This will always be empty for cluster-scoped resources when the user is authorized.","type":"string"},"tier":{"description":"The tier. This is only valid for tiered policies, and tiers.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerb":{"type":"object","required":["verb","resourceGroups"],"properties":{"resourceGroups":{"description":"The group of resource instances that are authorized for this verb.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceGroup"}},"verb":{"description":"The verb.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerbs":{"type":"object","properties":{"apiGroup":{"description":"The API group.","type":"string"},"resource":{"description":"The resource.","type":"string"},"verbs":{"description":"The set of authorized actions for this resource. For a specific verb, this contains the set of resources for which the user is authorized to perform that action. This is calculated to avoid duplication such that a single resource instance can only be associated with a single entry in this slice. This allows a consumer of this API to issue a minimal set of queries (e.g. watches) that cover, uniquely, the authorized set of resources.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerb"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AutoHostEndpointConfig":{"type":"object","properties":{"autoCreate":{"description":"AutoCreate enables automatic creation of host endpoints for every node. [Default: Disabled]","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.BGPConfigurationSpec":{"description":"BGPConfigurationSpec contains the values of the BGP configuration.","type":"object","properties":{"asNumber":{"description":"ASNumber is the default AS number used by a node. [Default: 64512]","type":"integer","format":"int64"},"communities":{"description":"Communities is a list of BGP community values and their arbitrary names for tagging routes.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Community"}},"extensions":{"description":"Extensions is a mapping of keys to values that can be used in custom BGP templates","type":"object","additionalProperties":{"type":"string"}},"listenPort":{"description":"ListenPort is the port where BGP protocol should listen. Defaults to 179","type":"integer","format":"int32"},"logSeverityScreen":{"description":"LogSeverityScreen is the log severity above which logs are sent to the stdout. [Default: INFO]","type":"string"},"nodeToNodeMeshEnabled":{"description":"NodeToNodeMeshEnabled sets whether full node to node BGP mesh is enabled. [Default: true]","type":"boolean"},"prefixAdvertisements":{"description":"PrefixAdvertisements contains per-prefix advertisement configuration.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.PrefixAdvertisement"}},"serviceClusterIPs":{"description":"ServiceClusterIPs are the CIDR blocks from which service cluster IPs are allocated. If specified, Calico will advertise these blocks, as well as any cluster IPs within them.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceClusterIPBlock"}},"serviceExternalIPs":{"description":"ServiceExternalIPs are the CIDR blocks for Kubernetes Service External IPs. Kubernetes Service ExternalIPs will only be advertised if they are within one of these blocks.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceExternalIPBlock"}},"serviceLoadBalancerIPs":{"description":"ServiceLoadBalancerIPs are the CIDR blocks for Kubernetes Service LoadBalancer IPs. Kubernetes Service status.LoadBalancer.Ingress IPs will only be advertised if they are within one of these blocks.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceLoadBalancerIPBlock"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPassword":{"description":"BGPPassword contains ways to specify a BGP password.","type":"object","properties":{"secretKeyRef":{"description":"Selects a key of a secret in the node pod's namespace.","$ref":"#/definitions/io.k8s.api.core.v1.SecretKeySelector"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPeerSpec":{"description":"BGPPeerSpec contains the specification for a BGPPeer resource.","type":"object","properties":{"asNumber":{"description":"The AS Number of the peer.","type":"integer","format":"int64"},"birdGatewayMode":{"description":"Specifies the BIRD \"gateway\" mode, i.e. method for computing the immediate next hop for each received route, for peerings generated by this BGPPeer resource. Default value \"Recursive\" means \"gateway recursive\". \"DirectIfDirectlyConnected\" means to configure \"gateway direct\" when the peer is directly connected.","type":"string"},"extensions":{"description":"Extensions is a mapping of keys to values that can be used in custom BGP templates","type":"object","additionalProperties":{"type":"string"}},"failureDetectionMode":{"description":"Specifies whether and how to detect loss of connectivity on the peerings generated by this BGPPeer resource. Default value \"None\" means nothing beyond BGP's own (slow) hold timer. \"BFDIfDirectlyConnected\" means to use BFD when the peer is directly connected.","type":"string"},"keepOriginalNextHop":{"description":"Option to keep the original nexthop field when routes are sent to a BGP Peer. Setting \"true\" configures the selected BGP Peers node to use the \"next hop keep;\" instead of \"next hop self;\"(default) in the specific branch of the Node on \"bird.cfg\".","type":"boolean"},"maxRestartTime":{"description":"Time to allow for software restart. When specified, this is configured as the graceful restart timeout when RestartMode is \"GracefulRestart\", and as the LLGR stale time when RestartMode is \"LongLivedGracefulRestart\". When not specified, the BIRD defaults are used, which are 120s for \"GracefulRestart\" and 3600s for \"LongLivedGracefulRestart\".","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"node":{"description":"The node name identifying the Calico node instance that is targeted by this peer. If this is not set, and no nodeSelector is specified, then this BGP peer selects all nodes in the cluster.","type":"string"},"nodeSelector":{"description":"Selector for the nodes that should have this peering. When this is set, the Node field must be empty.","type":"string"},"password":{"description":"Optional BGP password for the peerings generated by this BGPPeer resource.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPassword"},"peerIP":{"description":"The IP address of the peer followed by an optional port number to peer with. If port number is given, format should be `[\u003cIPv6\u003e]:port` or `\u003cIPv4\u003e:\u003cport\u003e` for IPv4. If optional port number is not set, and this peer IP and ASNumber belongs to a calico/node with ListenPort set in BGPConfiguration, then we use that port to peer.","type":"string"},"peerSelector":{"description":"Selector for the remote nodes to peer with. When this is set, the PeerIP and ASNumber fields must be empty. For each peering between the local node and selected remote nodes, we configure an IPv4 peering if both ends have NodeBGPSpec.IPv4Address specified, and an IPv6 peering if both ends have NodeBGPSpec.IPv6Address specified. The remote AS number comes from the remote node's NodeBGPSpec.ASNumber, or the global default if that is not set.","type":"string"},"restartMode":{"description":"Specifies restart behaviour to configure on the peerings generated by this BGPPeer resource. Default value \"GracefulRestart\" means traditional graceful restart. \"LongLivedGracefulRestart\" means LLGR according to draft-uttaro-idr-bgp-persistence-05.","type":"string"},"sourceAddress":{"description":"Specifies whether and how to configure a source address for the peerings generated by this BGPPeer resource. Default value \"UseNodeIP\" means to configure the node IP as the source address. \"None\" means not to configure a source address.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkFilter":{"description":"CISBenchmarkFilter provides filters for a set of benchmarks that match particular selection criteria.","type":"object","properties":{"benchmarkSelection":{"description":"BenchmarkSelection specifies which benchmarks this filter applies to. If not specified, applies to all.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkSelection"},"exclude":{"description":"Exclude is an array of test indices to exclude from the report.","type":"array","items":{"type":"string"}},"include":{"description":"Include is an array of test indices to show in the report. Is additive if IncludeUnscoredTests is true. Takes precedence over Exclude.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkParams":{"description":"CISBenchmarkParams contains the parameters for configuring a CIS benchmark report.","type":"object","properties":{"highThreshold":{"description":"Interpretted as a percentage to indicate at what levels of passing tests a node should be considered HIGH, MED, and LOW. - If \u003e= HighThreshold flag as high - Otherwise, if \u003e MedThreshold flag as med - Otherwise flag as low.","type":"integer","format":"int32"},"includeUnscoredTests":{"description":"Specifies if the report should also show results for scored/not-scored tests.","type":"boolean"},"medThreshold":{"type":"integer","format":"int32"},"numFailedTests":{"description":"Configure the number of top failed tests to show up on the report.","type":"integer","format":"int32"},"resultsFilters":{"description":"Benchmark results filters. The first matching set of filters is applied to each set of benchmark results. If there are no matching filters, the full set of benchmark results will be included in the report.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkFilter"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkSelection":{"description":"CISBenchmarkSelection selects a particular set of benchmarks.","type":"object","properties":{"kubernetesVersion":{"description":"KubernetesVersion is used select nodes that are running a specific version of kubelet. The full version need not be fully specified down to the patch level, in which case the significant parts of the version are matched. e.g. \"1.0\" will match versions \"1.0.1\" and \"1.0.2\" If not specified, matches all versions.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ClusterInformationSpec":{"description":"ClusterInformationSpec contains the values of describing the cluster.","type":"object","properties":{"calicoVersion":{"description":"CalicoVersion is the version of Calico that the cluster is running","type":"string"},"clusterGUID":{"description":"ClusterGUID is the GUID of the cluster","type":"string"},"clusterType":{"description":"ClusterType describes the type of the cluster","type":"string"},"cnxVersion":{"description":"CNXVersion is the version of CNX that the cluster is running","type":"string"},"datastoreReady":{"description":"DatastoreReady is used during significant datastore migrations to signal to components such as Felix that it should wait before accessing the datastore.","type":"boolean"},"variant":{"description":"Variant declares which variant of Calico should be active.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.Community":{"description":"Community contains standard or large community value and its name.","type":"object","properties":{"name":{"description":"Name given to community value.","type":"string"},"value":{"description":"Value must be of format `aa:nn` or `aa:nn:mm`. For standard community use `aa:nn` format, where `aa` and `nn` are 16 bit number. For large community use `aa:nn:mm` format, where `aa`, `nn` and `mm` are 32 bit number. Where, `aa` is an AS Number, `nn` and `mm` are per-AS identifier.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CompletedReportJob":{"description":"CompletedReportJob augments the ReportJob with completion details.","type":"object","required":["start","end","job"],"properties":{"end":{"description":"The end time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"job":{"description":"A reference to the report creation job if known.","$ref":"#/definitions/io.k8s.api.core.v1.ObjectReference"},"jobCompletionTime":{"description":"The time the report job completed.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"start":{"description":"The start time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ControllersConfig":{"description":"ControllersConfig enables and configures individual Kubernetes controllers","type":"object","properties":{"federatedServices":{"description":"FederatedServices enables and configures the federatedservices controller. Disabled by default.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.FederatedServicesControllerConfig"},"namespace":{"description":"Namespace enables and configures the namespace controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NamespaceControllerConfig"},"node":{"description":"Node enables and configures the node controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NodeControllerConfig"},"policy":{"description":"Policy enables and configures the policy controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.PolicyControllerConfig"},"serviceAccount":{"description":"ServiceAccount enables and configures the service account controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountControllerConfig"},"workloadEndpoint":{"description":"WorkloadEndpoint enables and configures the workload endpoint controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.WorkloadEndpointControllerConfig"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EgressSpec":{"type":"object","properties":{"namespaceSelector":{"description":"NamespaceSelector","type":"string"},"selector":{"description":"Selector","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointPort":{"type":"object","required":["name","protocol","port"],"properties":{"name":{"type":"string"},"port":{"type":"integer","format":"int32"},"protocol":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Protocol"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointsSelection":{"description":"EndpointsSelection is a set of selectors used to select the endpoints that are considered to be in-scope for the report. An empty selector is equivalent to all(). All three selectors are ANDed together.","type":"object","properties":{"namespaces":{"description":"Namespace match restricts endpoint selection to those in the selected namespaces.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NamesAndLabelsMatch"},"selector":{"description":"Selector, selects endpoints by endpoint labels. If omitted, all endpoints are included in the report data.","type":"string"},"serviceAccounts":{"description":"ServiceAccount match restricts endpoint selection to those in the selected service accounts.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NamesAndLabelsMatch"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EntityRule":{"description":"An EntityRule is a sub-component of a Rule comprising the match criteria specific to a particular entity (that is either the source or destination).\n\nA source EntityRule matches the source endpoint and originating traffic. A destination EntityRule matches the destination endpoint and terminating traffic.","type":"object","properties":{"domains":{"description":"Domains is an optional field, valid for egress Allow rules only, that restricts the rule to apply only to traffic to one of the specified domains. If this field is specified, Action must be Allow, and Nets and Selector must both be left empty.","type":"array","items":{"type":"string"}},"namespaceSelector":{"description":"NamespaceSelector is an optional field that contains a selector expression. Only traffic that originates from (or terminates at) endpoints within the selected namespaces will be matched. When both NamespaceSelector and Selector are defined on the same rule, then only workload endpoints that are matched by both selectors will be selected by the rule.\n\nFor NetworkPolicy, an empty NamespaceSelector implies that the Selector is limited to selecting only workload endpoints in the same namespace as the NetworkPolicy.\n\nFor NetworkPolicy, `global()` NamespaceSelector implies that the Selector is limited to selecting only GlobalNetworkSet or HostEndpoint.\n\nFor GlobalNetworkPolicy, an empty NamespaceSelector implies the Selector applies to workload endpoints across all namespaces.","type":"string"},"nets":{"description":"Nets is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) IP addresses in any of the given subnets.","type":"array","items":{"type":"string"}},"notNets":{"description":"NotNets is the negated version of the Nets field.","type":"array","items":{"type":"string"}},"notPorts":{"description":"NotPorts is the negated version of the Ports field. Since only some protocols have ports, if any ports are specified it requires the Protocol match in the Rule to be set to \"TCP\" or \"UDP\".","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"}},"notSelector":{"description":"NotSelector is the negated version of the Selector field. See Selector field for subtleties with negated selectors.","type":"string"},"ports":{"description":"Ports is an optional field that restricts the rule to only apply to traffic that has a source (destination) port that matches one of these ranges/values. This value is a list of integers or strings that represent ranges of ports.\n\nSince only some protocols have ports, if any ports are specified it requires the Protocol match in the Rule to be set to \"TCP\" or \"UDP\".","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"}},"selector":{"description":"Selector is an optional field that contains a selector expression (see Policy for sample syntax). Only traffic that originates from (terminates at) endpoints matching the selector will be matched.\n\nNote that: in addition to the negated version of the Selector (see NotSelector below), the selector expression syntax itself supports negation. The two types of negation are subtly different. One negates the set of matched endpoints, the other negates the whole match:\n\n\tSelector = \"!has(my_label)\" matches packets that are from other Calico-controlled\n\tendpoints that do not have the label \"my_label\".\n\n\tNotSelector = \"has(my_label)\" matches packets that are not from Calico-controlled\n\tendpoints that do have the label \"my_label\".\n\nThe effect is that the latter will accept packets from non-Calico sources whereas the former is limited to packets from Calico-controlled endpoints.","type":"string"},"serviceAccounts":{"description":"ServiceAccounts is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) a pod running as a matching service account.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountMatch"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ErrorCondition":{"type":"object","required":["type","message"],"properties":{"message":{"type":"string"},"type":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.FederatedServicesControllerConfig":{"description":"FederatedServicesControllerConfig configures the federated services controller, which syncs Kubernetes services from remote clusters.","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.FelixConfigurationSpec":{"description":"FelixConfigurationSpec contains the values of the Felix configuration.","type":"object","properties":{"allowIPIPPacketsFromWorkloads":{"description":"AllowIPIPPacketsFromWorkloads controls whether Felix will add a rule to drop IPIP encapsulated traffic from workloads [Default: false]","type":"boolean"},"allowVXLANPacketsFromWorkloads":{"description":"AllowVXLANPacketsFromWorkloads controls whether Felix will add a rule to drop VXLAN encapsulated traffic from workloads [Default: false]","type":"boolean"},"awsSrcDstCheck":{"description":"Set source-destination-check on AWS EC2 instances. Accepted value must be one of \"DoNothing\", \"Enabled\" or \"Disabled\". [Default: DoNothing]","type":"string"},"bpfConnectTimeLoadBalancingEnabled":{"description":"BPFConnectTimeLoadBalancingEnabled when in BPF mode, controls whether Felix installs the connection-time load balancer. The connect-time load balancer is required for the host to be able to reach Kubernetes services and it improves the performance of pod-to-service connections. The only reason to disable it is for debugging purposes. [Default: true]","type":"boolean"},"bpfDataIfacePattern":{"description":"BPFDataIfacePattern is a regular expression that controls which interfaces Felix should attach BPF programs to in order to catch traffic to/from the network. This needs to match the interfaces that Calico workload traffic flows over as well as any interfaces that handle incoming traffic to nodeports and services from outside the cluster. It should not match the workload interfaces (usually named cali...).","type":"string"},"bpfDisableUnprivileged":{"description":"BPFDisableUnprivileged, if enabled, Felix sets the kernel.unprivileged_bpf_disabled sysctl to disable unprivileged use of BPF. This ensures that unprivileged users cannot access Calico's BPF maps and cannot insert their own BPF programs to interfere with Calico's. [Default: true]","type":"boolean"},"bpfEnabled":{"description":"BPFEnabled, if enabled Felix will use the BPF dataplane. [Default: false]","type":"boolean"},"bpfExternalServiceMode":{"description":"BPFExternalServiceMode in BPF mode, controls how connections from outside the cluster to services (node ports and cluster IPs) are forwarded to remote workloads. If set to \"Tunnel\" then both request and response traffic is tunneled to the remote node. If set to \"DSR\", the request traffic is tunneled but the response traffic is sent directly from the remote node. In \"DSR\" mode, the remote node appears to use the IP of the ingress node; this requires a permissive L2 network. [Default: Tunnel]","type":"string"},"bpfKubeProxyEndpointSlicesEnabled":{"description":"BPFKubeProxyEndpointSlicesEnabled in BPF mode, controls whether Felix's embedded kube-proxy accepts EndpointSlices or not.","type":"boolean"},"bpfKubeProxyIptablesCleanupEnabled":{"description":"BPFKubeProxyIptablesCleanupEnabled, if enabled in BPF mode, Felix will proactively clean up the upstream Kubernetes kube-proxy's iptables chains. Should only be enabled if kube-proxy is not running. [Default: true]","type":"boolean"},"bpfKubeProxyMinSyncPeriod":{"description":"BPFKubeProxyMinSyncPeriod, in BPF mode, controls the minimum time between updates to the dataplane for Felix's embedded kube-proxy. Lower values give reduced set-up latency. Higher values reduce Felix CPU usage by batching up more work. [Default: 1s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"bpfLogLevel":{"description":"BPFLogLevel controls the log level of the BPF programs when in BPF dataplane mode. One of \"Off\", \"Info\", or \"Debug\". The logs are emitted to the BPF trace pipe, accessible with the command `tc exec bpf debug`. [Default: Off].","type":"string"},"captureDir":{"description":"CaptureDir controls directory to store file capture. [Default: /var/log/calico/pcap]","type":"string"},"captureMaxFiles":{"description":"CaptureMaxFiles controls number of rotated capture file to keep. [Default: 2]","type":"integer","format":"int32"},"captureMaxSizeBytes":{"description":"CaptureMaxSizeBytes controls the max size of a file capture. [Default: 10000000]","type":"integer","format":"int32"},"captureRotationSeconds":{"description":"CaptureRotationSeconds controls the time rotation of a packet capture. [Default: 3600]","type":"integer","format":"int32"},"chainInsertMode":{"description":"ChainInsertMode controls whether Felix hooks the kernel's top-level iptables chains by inserting a rule at the top of the chain or by appending a rule at the bottom. insert is the safe default since it prevents Calico's rules from being bypassed. If you switch to append mode, be sure that the other rules in the chains signal acceptance by falling through to the Calico rules, otherwise the Calico policy will be bypassed. [Default: insert]","type":"string"},"cloudWatchLogsAggregationKindForAllowed":{"description":"CloudWatchLogsAggregationKindForAllowed is used to choose the type of aggregation for flow log entries created for allowed connections. [Default: 2 - pod prefix name based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggreagation.","type":"integer","format":"int32"},"cloudWatchLogsAggregationKindForDenied":{"description":"CloudWatchLogsAggregationKindForDenied is used to choose the type of aggregation for flow log entries created for denied connections. [Default: 1 - source port based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggreagation.","type":"integer","format":"int32"},"cloudWatchLogsEnableHostEndpoint":{"description":"Deprecated: Use FlowLogsEnableHostEndpoint.","type":"boolean"},"cloudWatchLogsEnabledForAllowed":{"description":"CloudWatchLogsEnabledForAllowed is used to enable/disable flow logs entries created for allowed connections. Default is true. This parameter only takes effect when CloudWatchLogsReporterEnabled is set to true.","type":"boolean"},"cloudWatchLogsEnabledForDenied":{"description":"CloudWatchLogsEnabledForDenied is used to enable/disable flow logs entries created for denied flows. Default is true. This parameter only takes effect when CloudWatchLogsReporterEnabled is set to true.","type":"boolean"},"cloudWatchLogsFlushInterval":{"description":"Deprecated: Use FlowLogsFlushInterval instead.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"cloudWatchLogsIncludeLabels":{"description":"CloudWatchLogsIncludeLabels is used to configure if endpoint labels are included in a Flow log entry.","type":"boolean"},"cloudWatchLogsIncludePolicies":{"description":"CloudWatchLogsIncludePolicies is used to configure if policy information are included in a Flow log entry.","type":"boolean"},"cloudWatchLogsLogGroupName":{"description":"CloudWatchLogsLogGroupName configures the Log group to use for exporting flow logs. Defaults to \"tigera-flowlogs-\u003ccluster-guid\u003e\".","type":"string"},"cloudWatchLogsLogStreamName":{"description":"CloudWatchLogsLogStreamName configures the Log stream to use for exporting flow logs. Defaults to \"\u003cfelix-hostname\u003e_Flowlogs\".","type":"string"},"cloudWatchLogsReporterEnabled":{"description":"Enable Flow logs reporting to AWS CloudWatch.","type":"boolean"},"cloudWatchLogsRetentionDays":{"description":"Number of days for which to retain logs. See https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutRetentionPolicy.html for allowed values.","type":"integer","format":"int32"},"cloudWatchMetricsPushIntervalSecs":{"description":"CloudWatchMetricsPushInterval configures the interval at which Felix exports metrics to CloudWatch.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"cloudWatchMetricsReporterEnabled":{"description":"Enable reporting metrics to CloudWatch.","type":"boolean"},"cloudWatchNodeHealthPushIntervalSecs":{"description":"CloudWatchNodeHealthPushIntervalSecs configures the frequency of pushing the node health metrics to CloudWatch.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"cloudWatchNodeHealthStatusEnabled":{"description":"CloudWatchNodeHealthStatusEnabled enables pushing node health data to CloudWatch.","type":"boolean"},"dataplaneDriver":{"type":"string"},"debugDisableLogDropping":{"type":"boolean"},"debugMemoryProfilePath":{"type":"string"},"debugSimulateCalcGraphHangAfter":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"debugSimulateDataplaneHangAfter":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"defaultEndpointToHostAction":{"description":"DefaultEndpointToHostAction controls what happens to traffic that goes from a workload endpoint to the host itself (after the traffic hits the endpoint egress policy). By default Calico blocks traffic from workload endpoints to the host itself with an iptables \"DROP\" action. If you want to allow some or all traffic from endpoint to host, set this parameter to RETURN or ACCEPT. Use RETURN if you have your own rules in the iptables \"INPUT\" chain; Calico will insert its rules at the top of that chain, then \"RETURN\" packets to the \"INPUT\" chain once it has completed processing workload endpoint egress policy. Use ACCEPT to unconditionally accept packets from workloads after processing workload endpoint egress policy. [Default: Drop]","type":"string"},"deletedMetricsRetentionSecs":{"type":"integer","format":"int32"},"deviceRouteProtocol":{"description":"This defines the route protocol added to programmed device routes, by default this will be RTPROT_BOOT when left blank.","type":"integer","format":"int32"},"deviceRouteSourceAddress":{"description":"This is the source address to use on programmed device routes. By default the source address is left blank, leaving the kernel to choose the source address used.","type":"string"},"disableConntrackInvalidCheck":{"type":"boolean"},"dnsCacheEpoch":{"description":"An arbitrary number that can be changed, at runtime, to tell Felix to discard all its learnt DNS information. [Default: 0].","type":"integer","format":"int32"},"dnsCacheFile":{"description":"The name of the file that Felix uses to preserve learnt DNS information when restarting. [Default: \"/var/run/calico/felix-dns-cache.txt\"].","type":"string"},"dnsCacheSaveInterval":{"description":"The periodic interval at which Felix saves learnt DNS information to the cache file. [Default: 60s].","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"dnsExtraTTL":{"description":"Extra time to keep IPs and alias names that are learnt from DNS, in addition to each name or IP's advertised TTL. [Default: 0s].","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"dnsLogsFileAggregationKind":{"description":"DNSLogsFileAggregationKind is used to choose the type of aggregation for DNS log entries. [Default: 1 - client name prefix aggregation]. Accepted values are 0 and 1. 0 - No aggregation 1 - Aggregate over clients with the same name prefix","type":"integer","format":"int32"},"dnsLogsFileDirectory":{"description":"DNSLogsFileDirectory sets the directory where DNS log files are stored. [Default: /var/log/calico/dnslogs]","type":"string"},"dnsLogsFileEnabled":{"description":"DNSLogsFileEnabled controls logging DNS logs to a file. If false no DNS logging to file will occur. [Default: false]","type":"boolean"},"dnsLogsFileIncludeLabels":{"description":"DNSLogsFileIncludeLabels is used to configure if endpoint labels are included in a DNS log entry written to file. [Default: true]","type":"boolean"},"dnsLogsFileMaxFileSizeMB":{"description":"DNSLogsFileMaxFileSizeMB sets the max size in MB of DNS log files before rotation. [Default: 100]","type":"integer","format":"int32"},"dnsLogsFileMaxFiles":{"description":"DNSLogsFileMaxFiles sets the number of DNS log files to keep. [Default: 5]","type":"integer","format":"int32"},"dnsLogsFilePerNodeLimit":{"description":"Limit on the number of DNS logs that can be emitted within each flush interval. When this limit has been reached, Felix counts the number of unloggable DNS responses within the flush interval, and emits a WARNING log with that count at the same time as it flushes the buffered DNS logs. [Default: 0, meaning no limit]","type":"integer","format":"int32"},"dnsLogsFlushInterval":{"description":"DNSLogsFlushInterval configures the interval at which Felix exports DNS logs. [Default: 300s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"dnsLogsLatency":{"description":"DNSLogsLatency indicates to include measurements of DNS request/response latency in each DNS log. [Default: true]","type":"boolean"},"dnsTrustedServers":{"description":"The DNS servers that Felix should trust. Each entry here must be `\u003cip\u003e[:\u003cport\u003e]` - indicating an explicit DNS server IP - or `k8s-service:[\u003cnamespace\u003e/]\u003cname\u003e[:port]` - indicating a Kubernetes DNS service. `\u003cport\u003e` defaults to the first service port, or 53 for an IP, and `\u003cnamespace\u003e` to `kube-system`. An IPv6 address with a port must use the square brackets convention, for example `[fd00:83a6::12]:5353`.Note that Felix (calico-node) will need RBAC permission to read the details of each service specified by a `k8s-service:...` form. [Default: \"k8s-service:kube-dns\"].","type":"array","items":{"type":"string"}},"dropActionOverride":{"description":"DropActionOverride overrides the Drop action in Felix, optionally changing the behavior to Accept, and optionally adding Log. Possible values are Drop, LogAndDrop, Accept, LogAndAccept. [Default: Drop]","type":"string"},"egressIPRoutingRulePriority":{"description":"EgressIPRoutingRulePriority controls the priority value to use for the egress IP routing rule. [Default: 100]","type":"integer","format":"int32"},"egressIPSupport":{"description":"EgressIPSupport defines three different support modes for egress IP function. [Default: Disabled] - Disabled: Egress IP function is disabled. - EnabledPerNamespace: Egress IP function is enabled and can be configured on a per-namespace basis;\n per-pod egress annotations are ignored.\n- EnabledPerNamespaceOrPerPod: Egress IP function is enabled and can be configured per-namespace or per-pod,\n with per-pod egress annotations overriding namespace annotations.","type":"string"},"egressIPVXLANPort":{"description":"EgressIPVXLANPort is the port number of vxlan tunnel device for egress traffic. [Default: 4790]","type":"integer","format":"int32"},"egressIPVXLANVNI":{"description":"EgressIPVXLANVNI is the VNI ID of vxlan tunnel device for egress traffic. [Default: 4097]","type":"integer","format":"int32"},"endpointReportingDelay":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"endpointReportingEnabled":{"type":"boolean"},"externalNodesList":{"description":"ExternalNodesCIDRList is a list of CIDR's of external-non-calico-nodes which may source tunnel traffic and have the tunneled traffic be accepted at calico nodes.","type":"array","items":{"type":"string"}},"failsafeInboundHostPorts":{"description":"FailsafeInboundHostPorts is a comma-delimited list of UDP/TCP ports that Felix will allow incoming traffic to host endpoints on irrespective of the security policy. This is useful to avoid accidentally cutting off a host with incorrect configuration. Each port should be specified as tcp:\u003cport-number\u003e or udp:\u003cport-number\u003e. For back-compatibility, if the protocol is not specified, it defaults to \"tcp\". To disable all inbound host ports, use the value none. The default value allows ssh access and DHCP. [Default: tcp:22, udp:68, tcp:179, tcp:2379, tcp:2380, tcp:6443, tcp:6666, tcp:6667]","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ProtoPort"}},"failsafeOutboundHostPorts":{"description":"FailsafeOutboundHostPorts is a comma-delimited list of UDP/TCP ports that Felix will allow outgoing traffic from host endpoints to irrespective of the security policy. This is useful to avoid accidentally cutting off a host with incorrect configuration. Each port should be specified as tcp:\u003cport-number\u003e or udp:\u003cport-number\u003e. For back-compatibility, if the protocol is not specified, it defaults to \"tcp\". To disable all outbound host ports, use the value none. The default value opens etcd's standard ports to ensure that Felix does not get cut off from etcd as well as allowing DHCP and DNS. [Default: tcp:179, tcp:2379, tcp:2380, tcp:6443, tcp:6666, tcp:6667, udp:53, udp:67]","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ProtoPort"}},"featureDetectOverride":{"description":"FeatureDetectOverride is used to override the feature detection. Values are specified in a comma separated list with no spaces, example; \"SNATFullyRandom=true,MASQFullyRandom=false,RestoreSupportsLock=\". \"true\" or \"false\" will force the feature, empty or omitted values are auto-detected.","type":"string"},"flowLogsAggregationThresholdBytes":{"description":"FlowLogsAggregationThresholdBytes is used specify how far behind the external pipeline that reads flow logs can be. Default is 8192 bytes. This parameter only takes effect when FlowLogsDynamicAggregationEnabled is set to true.","type":"integer","format":"int32"},"flowLogsCollectProcessInfo":{"description":"FlowLogsCollectProcessInfo, if enabled Felix will load the kprobe BPF programs to collect process info. [Default: false]","type":"boolean"},"flowLogsCollectTcpStats":{"description":"FlowLogsCollectTcpStats enables flow logs reporting TCP socket stats","type":"boolean"},"flowLogsDynamicAggregationEnabled":{"description":"FlowLogsDynamicAggregationEnabled is used to enable/disable dynamically changing aggregation levels. Default is true.","type":"boolean"},"flowLogsEnableHostEndpoint":{"description":"FlowLogsEnableHostEndpoint enables Flow logs reporting for HostEndpoints.","type":"boolean"},"flowLogsEnableNetworkSets":{"description":"FlowLogsEnableNetworkSets enables Flow logs reporting for GlobalNetworkSets.","type":"boolean"},"flowLogsFileAggregationKindForAllowed":{"description":"FlowLogsFileAggregationKindForAllowed is used to choose the type of aggregation for flow log entries created for allowed connections. [Default: 2 - pod prefix name based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggreagation.","type":"integer","format":"int32"},"flowLogsFileAggregationKindForDenied":{"description":"FlowLogsFileAggregationKindForDenied is used to choose the type of aggregation for flow log entries created for denied connections. [Default: 1 - source port based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggregation. 3 - No destination ports based aggregation","type":"integer","format":"int32"},"flowLogsFileDirectory":{"description":"FlowLogsFileDirectory sets the directory where flow logs files are stored.","type":"string"},"flowLogsFileEnabled":{"description":"FlowLogsFileEnabled when set to true, enables logging flow logs to a file. If false no flow logging to file will occur.","type":"boolean"},"flowLogsFileEnabledForAllowed":{"description":"FlowLogsFileEnabledForAllowed is used to enable/disable flow logs entries created for allowed connections. Default is true. This parameter only takes effect when FlowLogsFileReporterEnabled is set to true.","type":"boolean"},"flowLogsFileEnabledForDenied":{"description":"FlowLogsFileEnabledForDenied is used to enable/disable flow logs entries created for denied flows. Default is true. This parameter only takes effect when FlowLogsFileReporterEnabled is set to true.","type":"boolean"},"flowLogsFileIncludeLabels":{"description":"FlowLogsFileIncludeLabels is used to configure if endpoint labels are included in a Flow log entry written to file.","type":"boolean"},"flowLogsFileIncludePolicies":{"description":"FlowLogsFileIncludePolicies is used to configure if policy information are included in a Flow log entry written to file.","type":"boolean"},"flowLogsFileIncludeService":{"description":"FlowLogsFileIncludeService is used to configure if the destination service is included in a Flow log entry written to file. The service information can only be included if the flow was explicitly determined to be directed at the service (e.g. when the pre-DNAT destination corresponds to the service ClusterIP and port).","type":"boolean"},"flowLogsFileMaxFileSizeMB":{"description":"FlowLogsFileMaxFileSizeMB sets the max size in MB of flow logs files before rotation.","type":"integer","format":"int32"},"flowLogsFileMaxFiles":{"description":"FlowLogsFileMaxFiles sets the number of log files to keep.","type":"integer","format":"int32"},"flowLogsFilePerFlowProcessLimit":{"description":"FlowLogsFilePerFlowProcessLimit, is used to specify the maximum number of flow log entries with distinct process information beyond which process information will be aggregated. [Default: 2]","type":"integer","format":"int32"},"flowLogsFlushInterval":{"description":"FlowLogsFlushInterval configures the interval at which Felix exports flow logs.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"flowLogsMaxOriginalIPsIncluded":{"description":"FlowLogsMaxOriginalIPsIncluded specifies the number of unique IP addresses (if relevant) that should be included in Flow logs.","type":"integer","format":"int32"},"flowLogsPositionFilePath":{"description":"FlowLogsPositionFilePath is used specify the position of the external pipeline that reads flow logs. Default is /var/log/calico/flows.log.pos. This parameter only takes effect when FlowLogsDynamicAggregationEnabled is set to true.","type":"string"},"genericXDPEnabled":{"description":"GenericXDPEnabled enables Generic XDP so network cards that don't support XDP offload or driver modes can use XDP. This is not recommended since it doesn't provide better performance than iptables. [Default: false]","type":"boolean"},"healthEnabled":{"type":"boolean"},"healthHost":{"type":"string"},"healthPort":{"type":"integer","format":"int32"},"interfaceExclude":{"description":"InterfaceExclude is a comma-separated list of interfaces that Felix should exclude when monitoring for host endpoints. The default value ensures that Felix ignores Kubernetes' IPVS dummy interface, which is used internally by kube-proxy. If you want to exclude multiple interface names using a single value, the list supports regular expressions. For regular expressions you must wrap the value with '/'. For example having values '/^kube/,veth1' will exclude all interfaces that begin with 'kube' and also the interface 'veth1'. [Default: kube-ipvs0]","type":"string"},"interfacePrefix":{"description":"InterfacePrefix is the interface name prefix that identifies workload endpoints and so distinguishes them from host endpoint interfaces. Note: in environments other than bare metal, the orchestrators configure this appropriately. For example our Kubernetes and Docker integrations set the 'cali' value, and our OpenStack integration sets the 'tap' value. [Default: cali]","type":"string"},"interfaceRefreshInterval":{"description":"InterfaceRefreshInterval is the period at which Felix rescans local interfaces to verify their state. The rescan can be disabled by setting the interval to 0.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"ipipEnabled":{"type":"boolean"},"ipipMTU":{"description":"IPIPMTU is the MTU to set on the tunnel device. See Configuring MTU [Default: 1440]","type":"integer","format":"int32"},"ipsecAllowUnsecuredTraffic":{"description":"IPSecAllowUnsecuredTraffic controls whether non-IPsec traffic is allowed in addition to IPsec traffic. Enabling this negates the anti-spoofing protections of IPsec but it is useful when migrating to/from IPsec. [Default: false]","type":"boolean"},"ipsecESPAlgorithm":{"description":"IPSecESAlgorithm sets IPSec ESP algorithm. Default is NIST suite B recommendation. [Default: aes128gcm16-ecp256]","type":"string"},"ipsecIKEAlgorithm":{"description":"IPSecIKEAlgorithm sets IPSec IKE algorithm. Default is NIST suite B recommendation. [Default: aes128gcm16-prfsha256-ecp256]","type":"string"},"ipsecLogLevel":{"description":"IPSecLogLevel controls log level for IPSec components. Set to None for no logging. A generic log level terminology is used [None, Notice, Info, Debug, Verbose]. [Default: Info]","type":"string"},"ipsecMode":{"description":"IPSecMode controls which mode IPSec is operating on. Default value means IPSec is not enabled. [Default: \"\"]","type":"string"},"ipsecPolicyRefreshInterval":{"description":"IPSecPolicyRefreshInterval is the interval at which Felix will check the kernel's IPsec policy tables and repair any inconsistencies. [Default: 600s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"ipsetsRefreshInterval":{"description":"IpsetsRefreshInterval is the period at which Felix re-checks all iptables state to ensure that no other process has accidentally broken Calico's rules. Set to 0 to disable iptables refresh. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesBackend":{"description":"IptablesBackend specifies which backend of iptables will be used. The default is legacy.","type":"string"},"iptablesFilterAllowAction":{"type":"string"},"iptablesLockFilePath":{"description":"IptablesLockFilePath is the location of the iptables lock file. You may need to change this if the lock file is not in its standard location (for example if you have mapped it into Felix's container at a different path). [Default: /run/xtables.lock]","type":"string"},"iptablesLockProbeInterval":{"description":"IptablesLockProbeInterval is the time that Felix will wait between attempts to acquire the iptables lock if it is not available. Lower values make Felix more responsive when the lock is contended, but use more CPU. [Default: 50ms]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesLockTimeout":{"description":"IptablesLockTimeout is the time that Felix will wait for the iptables lock, or 0, to disable. To use this feature, Felix must share the iptables lock file with all other processes that also take the lock. When running Felix inside a container, this requires the /run directory of the host to be mounted into the calico/node or calico/felix container. [Default: 0s disabled]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesMangleAllowAction":{"type":"string"},"iptablesMarkMask":{"description":"IptablesMarkMask is the mask that Felix selects its IPTables Mark bits from. Should be a 32 bit hexadecimal number with at least 8 bits set, none of which clash with any other mark bits in use on the system. [Default: 0xff000000]","type":"integer","format":"int64"},"iptablesNATOutgoingInterfaceFilter":{"type":"string"},"iptablesPostWriteCheckInterval":{"description":"IptablesPostWriteCheckInterval is the period after Felix has done a write to the dataplane that it schedules an extra read back in order to check the write was not clobbered by another process. This should only occur if another application on the system doesn't respect the iptables lock. [Default: 1s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesRefreshInterval":{"description":"IptablesRefreshInterval is the period at which Felix re-checks the IP sets in the dataplane to ensure that no other process has accidentally broken Calico's rules. Set to 0 to disable IP sets refresh. Note: the default for this value is lower than the other refresh intervals as a workaround for a Linux kernel bug that was fixed in kernel version 4.11. If you are using v4.11 or greater you may want to set this to, a higher value to reduce Felix CPU usage. [Default: 10s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"ipv6Support":{"type":"boolean"},"kubeNodePortRanges":{"description":"KubeNodePortRanges holds list of port ranges used for service node ports. Only used if felix detects kube-proxy running in ipvs mode. Felix uses these ranges to separate host and workload traffic. [Default: 30000:32767].","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"}},"l7LogsFileAggregationDestinationInfo":{"description":"L7LogsFileAggregationDestinationInfo is used to choose the type of aggregation for the destination metadata on L7 log entries. [Default: IncludeL7DestinationInfo - include destination metadata]. Accepted values are IncludeL7DestinationInfo and ExcludeL7DestinationInfo. IncludeL7DestinationInfo - Include destination metadata in the logs. ExcludeL7DestinationInfo - Aggregate over all other fields ignoring the destination aggregated name, namespace, and type.","type":"string"},"l7LogsFileAggregationHTTPHeaderInfo":{"description":"L7LogsFileAggregationHTTPHeaderInfo is used to choose the type of aggregation for HTTP header data on L7 log entries. [Default: ExcludeL7HTTPHeaderInfo - http header info removal]. Accepted values are IncludeL7HTTPHeaderInfo and ExcludeL7HTTPHeaderInfo. IncludeL7HTTPHeaderInfo - Include HTTP header data in the logs. ExcludeL7HTTPHeaderInfo - Aggregate over all other fields ignoring the user agent and log type.","type":"string"},"l7LogsFileAggregationHTTPMethod":{"description":"L7LogsFileAggregationHTTPMethod is used to choose the type of aggregation for the HTTP request method on L7 log entries. [Default: IncludeL7HTTPMethod - include the HTTP method]. Accepted values are IncludeL7HTTPMethod and ExcludeL7HTTPMethod. IncludeL7HTTPMethod - Include HTTP method in the logs. ExcludeL7HTTPMethod - Aggregate over all other fields ignoring the HTTP method.","type":"string"},"l7LogsFileAggregationNumURLPath":{"description":"L7LogsFileAggregationNumURLPath is used to choose the number of components in the url path to display. This allows for the url to be truncated in case parts of the path provide no value. Setting this value to negative will allow all parts of the path to be displayed. [Default: 5].","type":"integer","format":"int32"},"l7LogsFileAggregationResponseCode":{"description":"L7LogsFileAggregationResponseCode is used to choose the type of aggregation for the response code on L7 log entries. [Default: IncludeL7ResponseCode - include the response code]. Accepted values are IncludeL7ResponseCode and ExcludeL7ResponseCode. IncludeL7ResponseCode - Include the response code in the logs. ExcludeL7ResponseCode - Aggregate over all other fields ignoring the response code.","type":"string"},"l7LogsFileAggregationServiceInfo":{"description":"L7LogsFileAggregationServiceInfo is used to choose the type of aggregation for the service data on L7 log entries. [Default: IncludeL7ServiceInfo - include service data]. Accepted values are IncludeL7ServiceInfo and ExcludeL7ServiceInfo. IncludeL7ServiceInfo - Include service data in the logs. ExcludeL7ServiceInfo - Aggregate over all other fields ignoring the service name, namespace, and port.","type":"string"},"l7LogsFileAggregationSourceInfo":{"description":"L7LogsFileAggregationExcludeSourceInfo is used to choose the type of aggregation for the source metadata on L7 log entries. [Default: IncludeL7SourceInfo - include source metadata]. Accepted values are IncludeL7SourceInfo and ExcludeL7SourceInfo. IncludeL7SourceInfo - Include source metadata in the logs. ExcludeL7SourceInfo - Aggregate over all other fields ignoring the source aggregated name, namespace, and type.","type":"string"},"l7LogsFileAggregationTrimURL":{"description":"L7LogsFileAggregationTrimURL is used to choose the type of aggregation for the url on L7 log entries. [Default: IncludeL7FullURL - include the full URL up to however many path components are allowed by L7LogsFileAggregationNumURLPath]. Accepted values are 0 and 1. IncludeL7FullURL - Include the full URL up to however many path components are allowed by L7LogsFileAggregationNumURLPath. TrimURLQuery - Aggregate over all other fields ignoring the query parameters on the URL. TrimURLQueryAndPath - Aggregate over all other fields and the base URL only. ExcludeL7URL - Aggregate over all other fields ignoring the URL entirely.","type":"string"},"l7LogsFileAggregationURLCharLimit":{"description":"Limit on the length of the URL collected in L7 logs. When a URL length reaches this limit it is sliced off, and the sliced URL is sent to log storage. [Default: 250]","type":"integer","format":"int32"},"l7LogsFileDirectory":{"description":"L7LogsFileDirectory sets the directory where L7 log files are stored. [Default: /var/log/calico/l7logs]","type":"string"},"l7LogsFileEnabled":{"description":"L7LogsFileEnabled controls logging L7 logs to a file. If false no L7 logging to file will occur. [Default: false]","type":"boolean"},"l7LogsFileMaxFileSizeMB":{"description":"L7LogsFileMaxFileSizeMB sets the max size in MB of L7 log files before rotation. [Default: 100]","type":"integer","format":"int32"},"l7LogsFileMaxFiles":{"description":"L7LogsFileMaxFiles sets the number of L7 log files to keep. [Default: 5]","type":"integer","format":"int32"},"l7LogsFilePerNodeLimit":{"description":"Limit on the number of L7 logs that can be emitted within each flush interval. When this limit has been reached, Felix counts the number of unloggable L7 responses within the flush interval, and emits a WARNING log with that count at the same time as it flushes the buffered L7 logs. [Default: 0, meaning no limit]","type":"integer","format":"int32"},"l7LogsFlushInterval":{"description":"L7LogsFlushInterval configures the interval at which Felix exports L7 logs. [Default: 300s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"logDropActionOverride":{"description":"LogDropActionOverride specifies whether or not to include the DropActionOverride in the logs when it is triggered.","type":"boolean"},"logFilePath":{"description":"LogFilePath is the full path to the Felix log. Set to none to disable file logging. [Default: /var/log/calico/felix.log]","type":"string"},"logPrefix":{"description":"LogPrefix is the log prefix that Felix uses when rendering LOG rules. [Default: calico-packet]","type":"string"},"logSeverityFile":{"description":"LogSeverityFile is the log severity above which logs are sent to the log file. [Default: Info]","type":"string"},"logSeverityScreen":{"description":"LogSeverityScreen is the log severity above which logs are sent to the stdout. [Default: Info]","type":"string"},"logSeveritySys":{"description":"LogSeveritySys is the log severity above which logs are sent to the syslog. Set to None for no logging to syslog. [Default: Info]","type":"string"},"maxIpsetSize":{"type":"integer","format":"int32"},"metadataAddr":{"description":"MetadataAddr is the IP address or domain name of the server that can answer VM queries for cloud-init metadata. In OpenStack, this corresponds to the machine running nova-api (or in Ubuntu, nova-api-metadata). A value of none (case insensitive) means that Felix should not set up any NAT rule for the metadata path. [Default: 127.0.0.1]","type":"string"},"metadataPort":{"description":"MetadataPort is the port of the metadata server. This, combined with global.MetadataAddr (if not 'None'), is used to set up a NAT rule, from 169.254.169.254:80 to MetadataAddr:MetadataPort. In most cases this should not need to be changed [Default: 8775].","type":"integer","format":"int32"},"mtuIfacePattern":{"description":"MTUIfacePattern is a regular expression that controls which interfaces Felix should scan in order to calculate the host's MTU. This should not match workload interfaces (usually named cali...).","type":"string"},"natOutgoingAddress":{"description":"NATOutgoingAddress specifies an address to use when performing source NAT for traffic in a natOutgoing pool that is leaving the network. By default the address used is an address on the interface the traffic is leaving on (ie it uses the iptables MASQUERADE target)","type":"string"},"natPortRange":{"description":"NATPortRange specifies the range of ports that is used for port mapping when doing outgoing NAT. When unset the default behavior of the network stack is used.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"},"netlinkTimeout":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"nfNetlinkBufSize":{"type":"string"},"openstackRegion":{"description":"OpenstackRegion is the name of the region that a particular Felix belongs to. In a multi-region Calico/OpenStack deployment, this must be configured somehow for each Felix (here in the datamodel, or in felix.cfg or the environment on each compute node), and must match the [calico] openstack_region value configured in neutron.conf on each node. [Default: Empty]","type":"string"},"policySyncPathPrefix":{"description":"PolicySyncPathPrefix is used to by Felix to communicate policy changes to external services, like Application layer policy. [Default: Empty]","type":"string"},"prometheusGoMetricsEnabled":{"description":"PrometheusGoMetricsEnabled disables Go runtime metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. [Default: true]","type":"boolean"},"prometheusMetricsCAFile":{"type":"string"},"prometheusMetricsCertFile":{"description":"TLS credentials for this port.","type":"string"},"prometheusMetricsEnabled":{"description":"PrometheusMetricsEnabled enables the Prometheus metrics server in Felix if set to true. [Default: false]","type":"boolean"},"prometheusMetricsHost":{"description":"PrometheusMetricsHost is the host that the Prometheus metrics server should bind to. [Default: empty]","type":"string"},"prometheusMetricsKeyFile":{"type":"string"},"prometheusMetricsPort":{"description":"PrometheusMetricsPort is the TCP port that the Prometheus metrics server should bind to. [Default: 9091]","type":"integer","format":"int32"},"prometheusProcessMetricsEnabled":{"description":"PrometheusProcessMetricsEnabled disables process metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. [Default: true]","type":"boolean"},"prometheusReporterCAFile":{"type":"string"},"prometheusReporterCertFile":{"type":"string"},"prometheusReporterEnabled":{"description":"Felix Denied Packet Metrics configuration parameters.","type":"boolean"},"prometheusReporterKeyFile":{"type":"string"},"prometheusReporterPort":{"type":"integer","format":"int32"},"removeExternalRoutes":{"description":"Whether or not to remove device routes that have not been programmed by Felix. Disabling this will allow external applications to also add device routes. This is enabled by default which means we will remove externally added routes.","type":"boolean"},"reportingInterval":{"description":"ReportingInterval is the interval at which Felix reports its status into the datastore or 0 to disable. Must be non-zero in OpenStack deployments. [Default: 30s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"reportingTTL":{"description":"ReportingTTL is the time-to-live setting for process-wide status reports. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"routeRefreshInterval":{"description":"RouteRefreshInterval is the period at which Felix re-checks the routes in the dataplane to ensure that no other process has accidentally broken Calico's rules. Set to 0 to disable route refresh. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"routeSource":{"description":"RouteSource configures where Felix gets its routing information. - WorkloadIPs: use workload endpoints to construct routes. - CalicoIPAM: the default - use IPAM data to construct routes.","type":"string"},"routeTableRange":{"description":"Calico programs additional Linux route tables for various purposes. RouteTableRange specifies the indices of the route tables that Calico should use.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.RouteTableRange"},"serviceLoopPrevention":{"description":"When service IP advertisement is enabled, prevent routing loops to service IPs that are not in use, by dropping or rejecting packets that do not get DNAT'd by kube-proxy. Unless set to \"Disabled\", in which case such routing loops continue to be allowed. [Default: Drop]","type":"string"},"sidecarAccelerationEnabled":{"description":"SidecarAccelerationEnabled enables experimental sidecar acceleration [Default: false]","type":"boolean"},"statsDumpFilePath":{"type":"string"},"syslogReporterAddress":{"type":"string"},"syslogReporterNetwork":{"type":"string"},"usageReportingEnabled":{"description":"UsageReportingEnabled reports anonymous Calico version number and cluster size to projectcalico.org. Logs warnings returned by the usage server. For example, if a significant security vulnerability has been discovered in the version of Calico being used. [Default: true]","type":"boolean"},"usageReportingInitialDelay":{"description":"UsageReportingInitialDelay controls the minimum delay before Felix makes a report. [Default: 300s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"usageReportingInterval":{"description":"UsageReportingInterval controls the interval at which Felix makes reports. [Default: 86400s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"useInternalDataplaneDriver":{"type":"boolean"},"vxlanEnabled":{"type":"boolean"},"vxlanMTU":{"description":"VXLANMTU is the MTU to set on the tunnel device. See Configuring MTU [Default: 1440]","type":"integer","format":"int32"},"vxlanPort":{"type":"integer","format":"int32"},"vxlanVNI":{"type":"integer","format":"int32"},"windowsFlowLogsFileDirectory":{"description":"WindowsFlowLogsFileDirectory sets the directory where flow logs files are stored on Windows nodes. [Default: \"c:\\TigeraCalico\\flowlogs\"].","type":"string"},"windowsFlowLogsPositionFilePath":{"description":"WindowsFlowLogsPositionFilePath is used to specify the position of the external pipeline that reads flow logs on Windows nodes. [Default: \"c:\\TigeraCalico\\flowlogs\\flows.log.pos\"]. This parameter only takes effect when FlowLogsDynamicAggregationEnabled is set to true.","type":"string"},"windowsNetworkName":{"description":"WindowsNetworkName specifies which Windows HNS networks Felix should operate on. The default is to match networks that start with \"calico\". Supports regular expression syntax.","type":"string"},"windowsStatsDumpFilePath":{"description":"WindowsStatsDumpFilePath is used to specify the path of the stats dump file on Windows nodes. [Default: \"c:\\TigeraCalico\\stats\\dump\"]","type":"string"},"wireguardEnabled":{"description":"WireguardEnabled controls whether Wireguard is enabled. [Default: false]","type":"boolean"},"wireguardInterfaceName":{"description":"WireguardInterfaceName specifies the name to use for the Wireguard interface. [Default: wg.calico]","type":"string"},"wireguardListeningPort":{"description":"WireguardListeningPort controls the listening port used by Wireguard. [Default: 51820]","type":"integer","format":"int32"},"wireguardMTU":{"description":"WireguardMTU controls the MTU on the Wireguard interface. See Configuring MTU [Default: 1420]","type":"integer","format":"int32"},"wireguardRoutingRulePriority":{"description":"WireguardRoutingRulePriority controls the priority value to use for the Wireguard routing rule. [Default: 99]","type":"integer","format":"int32"},"xdpEnabled":{"description":"XDPEnabled enables XDP acceleration for suitable untracked incoming deny rules. [Default: true]","type":"boolean"},"xdpRefreshInterval":{"description":"XDPRefreshInterval is the period at which Felix re-checks all XDP state to ensure that no other process has accidentally broken Calico's BPF maps or attached programs. Set to 0 to disable XDP refresh. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertSpec":{"type":"object","required":["description","severity","dataSet"],"properties":{"aggregateBy":{"type":"array","items":{"type":"string"}},"condition":{"type":"string"},"dataSet":{"type":"string"},"description":{"type":"string"},"field":{"type":"string"},"lookback":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"metric":{"type":"string"},"period":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"query":{"type":"string"},"severity":{"type":"integer","format":"int32"},"summary":{"type":"string"},"threshold":{"type":"number","format":"double"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertStatus":{"type":"object","required":["active","healthy"],"properties":{"active":{"type":"boolean"},"errorConditions":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ErrorCondition"}},"executionState":{"type":"string"},"healthy":{"type":"boolean"},"lastEvent":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"lastExecuted":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"lastUpdate":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkPolicySpec":{"type":"object","properties":{"applyOnForward":{"description":"ApplyOnForward indicates to apply the rules in this policy on forward traffic.","type":"boolean"},"doNotTrack":{"description":"DoNotTrack indicates whether packets matched by the rules in this policy should go through the data plane's connection tracking, such as Linux conntrack. If True, the rules in this policy are applied before any data plane connection tracking, and packets allowed by this policy are marked as not to be tracked.","type":"boolean"},"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"namespaceSelector":{"description":"NamespaceSelector is an optional field for an expression used to select a pod based on namespaces.","type":"string"},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"preDNAT":{"description":"PreDNAT indicates to apply the rules in this policy before any DNAT.","type":"boolean"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress rules are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSpec":{"description":"GlobalNetworkSetSpec contains the specification for a NetworkSet resource.","type":"object","properties":{"allowedEgressDomains":{"description":"The list of domain names that belong to this set and are honored in egress allow rules only. Domain names specified here only work to allow egress traffic from the cluster to external destinations. They don't work to _deny_ traffic to destinations specified by domain name, or to allow ingress traffic from _sources_ specified by domain name.","type":"array","items":{"type":"string"}},"nets":{"description":"The list of IP networks that belong to this set.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSync":{"type":"object","properties":{"labels":{"type":"object","additionalProperties":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedSpec":{"description":"GlobalThreatFeedSpec contains the specification of a GlobalThreatFeed resource.","type":"object","properties":{"content":{"description":"Content describes the kind of data the data feed provides.","type":"string"},"globalNetworkSet":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSync"},"pull":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Pull"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedStatus":{"type":"object","required":["lastSuccessfulSync","lastSuccessfulSearch","errorConditions"],"properties":{"errorConditions":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ErrorCondition"}},"lastSuccessfulSearch":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"lastSuccessfulSync":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeader":{"type":"object","required":["name"],"properties":{"name":{"type":"string"},"value":{"type":"string"},"valueFrom":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeaderSource"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeaderSource":{"type":"object","properties":{"configMapKeyRef":{"description":"Selects a key of a ConfigMap.","$ref":"#/definitions/io.k8s.api.core.v1.ConfigMapKeySelector"},"secretKeyRef":{"description":"Selects a key of a secret in the pod's namespace","$ref":"#/definitions/io.k8s.api.core.v1.SecretKeySelector"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPMatch":{"description":"HTTPMatch is an optional field that apply only to HTTP requests The Methods and Path fields are joined with AND","type":"object","properties":{"methods":{"description":"Methods is an optional field that restricts the rule to apply only to HTTP requests that use one of the listed HTTP Methods (e.g. GET, PUT, etc.) Multiple methods are OR'd together.","type":"array","items":{"type":"string"}},"paths":{"description":"Paths is an optional field that restricts the rule to apply to HTTP requests that use one of the listed HTTP Paths. Multiple paths are OR'd together. e.g: - exact: /foo - prefix: /bar NOTE: Each entry may ONLY specify either a `exact` or a `prefix` match. The validator will check for it.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPath"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPath":{"description":"HTTPPath specifies an HTTP path to match. It may be either of the form: exact: \u003cpath\u003e: which matches the path exactly or prefix: \u003cpath-prefix\u003e: which matches the path prefix","type":"object","properties":{"exact":{"type":"string"},"prefix":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPull":{"type":"object","required":["url"],"properties":{"format":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormat"},"headers":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeader"}},"url":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HostEndpointSpec":{"description":"HostEndpointSpec contains the specification for a HostEndpoint resource.","type":"object","properties":{"expectedIPs":{"description":"The expected IP addresses (IPv4 and IPv6) of the endpoint. If \"InterfaceName\" is not present, Calico will look for an interface matching any of the IPs in the list and apply policy to that. Note:\n\tWhen using the selector match criteria in an ingress or egress security Policy\n\tor Profile, Calico converts the selector into a set of IP addresses. For host\n\tendpoints, the ExpectedIPs field is used for that purpose. (If only the interface\n\tname is specified, Calico does not learn the IPs of the interface for use in match\n\tcriteria.)","type":"array","items":{"type":"string"}},"interfaceName":{"description":"Either \"*\", or the name of a specific Linux interface to apply policy to; or empty. \"*\" indicates that this HostEndpoint governs all traffic to, from or through the default network namespace of the host named by the \"Node\" field; entering and leaving that namespace via any interface, including those from/to non-host-networked local workloads.\n\nIf InterfaceName is not \"*\", this HostEndpoint only governs traffic that enters or leaves the host through the specific interface named by InterfaceName, or - when InterfaceName is empty - through the specific interface that has one of the IPs in ExpectedIPs. Therefore, when InterfaceName is empty, at least one expected IP must be specified. Only external interfaces (such as \"eth0\") are supported here; it isn't possible for a HostEndpoint to protect traffic through a specific local workload interface.\n\nNote: Only some kinds of policy are implemented for \"*\" HostEndpoints; initially just pre-DNAT policy. Please check Calico documentation for the latest position.","type":"string"},"node":{"description":"The node name identifying the Calico node instance.","type":"string"},"ports":{"description":"Ports contains the endpoint's named ports, which may be referenced in security policy rules.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointPort"}},"profiles":{"description":"A list of identifiers of security Profile objects that apply to this endpoint. Each profile is applied in the order that they appear in this list. Profile rules are applied after the selector-based security policy.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ICMPFields":{"description":"ICMPFields defines structure for ICMP and NotICMP sub-struct for ICMP code and type","type":"object","properties":{"code":{"description":"Match on a specific ICMP code. If specified, the Type value must also be specified. This is a technical limitation imposed by the kernel's iptables firewall, which Calico uses to enforce the rule.","type":"integer","format":"int32"},"type":{"description":"Match on a specific ICMP type. For example a value of 8 refers to ICMP Echo Request (i.e. pings).","type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.IPPoolSpec":{"description":"IPPoolSpec contains the specification for an IPPool resource.","type":"object","required":["cidr"],"properties":{"blockSize":{"description":"The block size to use for IP address assignments from this pool. Defaults to 26 for IPv4 and 112 for IPv6.","type":"integer","format":"int32"},"cidr":{"description":"The pool CIDR.","type":"string"},"disabled":{"description":"When disabled is true, Calico IPAM will not assign addresses from this pool.","type":"boolean"},"ipip":{"description":"Deprecated: this field is only used for APIv1 backwards compatibility. Setting this field is not allowed, this field is for internal use only.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v1.IPIPConfiguration"},"ipipMode":{"description":"Contains configuration for IPIP tunneling for this pool. If not specified, then this is defaulted to \"Never\" (i.e. IPIP tunneling is disabled).","type":"string"},"nat-outgoing":{"description":"Deprecated: this field is only used for APIv1 backwards compatibility. Setting this field is not allowed, this field is for internal use only.","type":"boolean"},"natOutgoing":{"description":"When nat-outgoing is true, packets sent from Calico networked containers in this pool to destinations outside of this pool will be masqueraded.","type":"boolean"},"nodeSelector":{"description":"Allows IPPool to allocate for a specific node by label selector.","type":"string"},"vxlanMode":{"description":"Contains configuration for VXLAN tunneling for this pool. If not specified, then this is defaulted to \"Never\" (i.e. VXLAN tunneling is disabled).","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationSpec":{"description":"KubeControllersConfigurationSpec contains the values of the Kubernetes controllers configuration.","type":"object","required":["controllers"],"properties":{"controllers":{"description":"Controllers enables and configures individual Kubernetes controllers","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ControllersConfig"},"etcdV3CompactionPeriod":{"description":"EtcdV3CompactionPeriod is the period between etcdv3 compaction requests. Set to 0 to disable. [Default: 10m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"healthChecks":{"description":"HealthChecks enables or disables support for health checks [Default: Enabled]","type":"string"},"logSeverityScreen":{"description":"LogSeverityScreen is the log severity above which logs are sent to the stdout. [Default: Info]","type":"string"},"prometheusMetricsPort":{"description":"PrometheusMetricsPort is the TCP port that the Prometheus metrics server should bind to. Set to 0 to disable. [Default: 9094]","type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationStatus":{"description":"KubeControllersConfigurationStatus represents the status of the configuration. It's useful for admins to be able to see the actual config that was applied, which can be modified by environment variables on the kube-controllers process.","type":"object","properties":{"environmentVars":{"description":"EnvironmentVars contains the environment variables on the kube-controllers that influenced the RunningConfig.","type":"object","additionalProperties":{"type":"string"}},"runningConfig":{"description":"RunningConfig contains the effective config that is running in the kube-controllers pod, after merging the API resource with any environment variables.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationSpec"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeySpec":{"description":"LicenseKeySpec contains the license key itself.","type":"object","required":["token"],"properties":{"certificate":{"description":"Certificate is used to validate the token.","type":"string"},"token":{"description":"Token is the JWT containing the license claims","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeyStatus":{"description":"LicenseKeyStatus contains the license key information.","type":"object","properties":{"expiry":{"description":"Expiry is the expiry date of License","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"features":{"description":"List of features that are available via the applied license","type":"array","items":{"type":"string"}},"maxnodes":{"description":"Maximum Number of Allowed Nodes","type":"integer","format":"int32"},"package":{"description":"License package defines type of Calico license that is being enforced","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterSpec":{"description":"ManagedClusterSpec contains the specification of a ManagedCluster resource.","type":"object","properties":{"installationManifest":{"description":"Field to store dynamically generated manifest for installing component into the actual application cluster corresponding to this Managed Cluster","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatus":{"type":"object","properties":{"conditions":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatusCondition"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatusCondition":{"description":"Condition contains various status information","type":"object","required":["status","type"],"properties":{"message":{"type":"string"},"reason":{"type":"string"},"status":{"type":"string"},"type":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NamesAndLabelsMatch":{"description":"NamesAndLabelsMatch is used to specify resource matches using both label and name selection.","type":"object","properties":{"names":{"description":"Names is an optional field that specifies a set of resources by name.","type":"array","items":{"type":"string"}},"selector":{"description":"Selector is an optional field that selects a set of resources by label. If both Names and Selector are specified then they are AND'ed.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NamespaceControllerConfig":{"description":"NamespaceControllerConfig configures the service account controller, which syncs Kubernetes service accounts to Calico profiles (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkPolicySpec":{"type":"object","properties":{"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkSetSpec":{"description":"NetworkSetSpec contains the specification for a NetworkSet resource.","type":"object","properties":{"allowedEgressDomains":{"description":"The list of domain names that belong to this set and are honored in egress allow rules only. Domain names specified here only work to allow egress traffic from the cluster to external destinations. They don't work to _deny_ traffic to destinations specified by domain name, or to allow ingress traffic from _sources_ specified by domain name.","type":"array","items":{"type":"string"}},"nets":{"description":"The list of IP networks that belong to this set.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NodeControllerConfig":{"description":"NodeControllerConfig configures the node controller, which automatically cleans up configuration for nodes that no longer exist. Optionally, it can create host endpoints for all Kubernetes nodes.","type":"object","properties":{"hostEndpoint":{"description":"HostEndpoint controls syncing nodes to host endpoints. Disabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AutoHostEndpointConfig"},"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"syncLabels":{"description":"SyncLabels controls whether to copy Kubernetes node labels to Calico nodes. [Default: Enabled]","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.PacketCaptureSpec":{"description":"PacketCaptureSpec contains the values of the packet capture.","type":"object","properties":{"selector":{"description":"The selector is an expression used to pick out the endpoints that the policy should be applied to. The selector will only match endpoints in the same namespace as the PacketCapture resource.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.PolicyControllerConfig":{"description":"PolicyControllerConfig configures the network policy controller, which syncs Kubernetes policies to Calico policies (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.PrefixAdvertisement":{"description":"PrefixAdvertisement configures advertisement properties for the specified CIDR.","type":"object","properties":{"cidr":{"description":"CIDR for which properties should be advertised.","type":"string"},"communities":{"description":"Communities can be list of either community names already defined in `Specs.Communities` or community value of format `aa:nn` or `aa:nn:mm`. For standard community use `aa:nn` format, where `aa` and `nn` are 16 bit number. For large community use `aa:nn:mm` format, where `aa`, `nn` and `mm` are 32 bit number. Where,`aa` is an AS Number, `nn` and `mm` are per-AS identifier.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ProfileSpec":{"description":"ProfileSpec contains the specification for a security Profile resource.","type":"object","properties":{"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"egressGateway":{"description":"Egress control.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EgressSpec"},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"labelsToApply":{"description":"An option set of labels to apply to each endpoint (in addition to their own labels) referencing this profile. If labels configured on the endpoint have keys matching those labels inherited from the profile, the endpoint label values take precedence.","type":"object","additionalProperties":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ProtoPort":{"description":"ProtoPort is combination of protocol and port, both must be specified.","type":"object","required":["protocol","port"],"properties":{"port":{"type":"integer","format":"int32"},"protocol":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.Pull":{"type":"object","required":["http"],"properties":{"http":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPull"},"period":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.RemoteClusterConfigurationSpec":{"description":"RemoteClusterConfigurationSpec contains the values of describing the cluster.","type":"object","properties":{"clusterAccessSecret":{"description":"Specifies a Secret to read for the RemoteClusterconfiguration. If defined all datastore configuration in this struct will be cleared and overwritten with the appropriate fields in the Secret.","$ref":"#/definitions/io.k8s.api.core.v1.ObjectReference"},"datastoreType":{"description":"Indicates the datastore to use. If unspecified, defaults to etcdv3","type":"string"},"etcdCACert":{"type":"string"},"etcdCACertFile":{"description":"Path to the etcd Certificate Authority file. Valid if DatastoreType is etcdv3.","type":"string"},"etcdCert":{"type":"string"},"etcdCertFile":{"description":"Path to the etcd client certificate. Valid if DatastoreType is etcdv3.","type":"string"},"etcdEndpoints":{"description":"A comma separated list of etcd endpoints. Valid if DatastoreType is etcdv3. [Default: ]","type":"string"},"etcdKey":{"description":"These config file parameters are to support inline certificates, keys and CA / Trusted certificate.","type":"string"},"etcdKeyFile":{"description":"Path to the etcd key file. Valid if DatastoreType is etcdv3.","type":"string"},"etcdPassword":{"description":"Password for the given user name. Valid if DatastoreType is etcdv3.","type":"string"},"etcdUsername":{"description":"User name for RBAC. Valid if DatastoreType is etcdv3.","type":"string"},"k8sAPIEndpoint":{"description":"Location of the Kubernetes API. Not required if using kubeconfig. Valid if DatastoreType is kubernetes.","type":"string"},"k8sAPIToken":{"description":"Token to be used for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"k8sCAFile":{"description":"Location of a CA for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"k8sCertFile":{"description":"Location of a client certificate for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"k8sInsecureSkipTLSVerify":{"type":"boolean"},"k8sKeyFile":{"description":"Location of a client key for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"kubeconfig":{"description":"When using the Kubernetes datastore, the location of a kubeconfig file. Valid if DatastoreType is kubernetes.","type":"string"},"kubeconfigInline":{"description":"This is an alternative to Kubeconfig and if specified overrides Kubeconfig. This contains the contents that would normally be in the file pointed at by Kubeconfig.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportJob":{"description":"ReportJob contains","type":"object","required":["start","end","job"],"properties":{"end":{"description":"The end time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"job":{"description":"A reference to the report creation job if known.","$ref":"#/definitions/io.k8s.api.core.v1.ObjectReference"},"start":{"description":"The start time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportSpec":{"description":"ReportSpec contains the values of the GlobalReport.","type":"object","required":["reportType"],"properties":{"cis":{"description":"This field contain all the parameters for configuring a CIS benchmark report.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkParams"},"endpoints":{"description":"Endpoints is used to specify which endpoints are in-scope and stored in the generated report data. Only used if endpoints data and/or audit logs are gathered in the report. If omitted, treated as everything in-scope.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointsSelection"},"jobNodeSelector":{"description":"The node selector used to specify which nodes the report job may be scheduled on.","type":"object","additionalProperties":{"type":"string"}},"reportType":{"description":"The name of the report type.","type":"string"},"schedule":{"description":"The report schedule specified in cron format. This specifies both the start and end times of each report, where the end time of one report becomes the start time of the next report. Separate jobs are created to generate a report, and the job generates the report data from archived audit and traffic data. To ensure this data is actually archived, the jobs to generate each report starts at a configurable time *after* the end time of the report that is being generated. The default job start delay is 30m, but is configurable through the compliance-controller environments. The cron format has minute accuracy, but only up to two values may be configured for the minute column which means you may only have at most two reports for each hour period.","type":"string"},"suspend":{"description":"This flag tells the controller to suspend subsequent jobs for generating reports, it does not apply to already started jobs. If jobs are resumed then the controller will start creating jobs for any reports that were missed while the job was suspended.","type":"boolean"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportStatus":{"description":"ReportStatus contains the status of the automated report generation.","type":"object","properties":{"activeReportJobs":{"description":"The set of active report jobs.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportJob"}},"lastFailedReportJobs":{"description":"The configured report jobs that have failed.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CompletedReportJob"}},"lastScheduledReportJob":{"description":"The last scheduled report job.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportJob"},"lastSuccessfulReportJobs":{"description":"The configured report jobs that have completed successfully.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CompletedReportJob"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTemplate":{"description":"ReportTemplate defines a template used to render a report into downloadable or UI compatible format.","type":"object","properties":{"description":{"description":"A user-facing description of the template.","type":"string"},"name":{"description":"The name of this template. This should be unique across all template names within a ReportType. This will be used by the UI as the suffix of the downloadable file name.","type":"string"},"template":{"description":"The base-64 encoded go template used to render the report data.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTypeSpec":{"description":"ReportTypeSpec contains the various templates, and configuration used to render a specific type of report.","type":"object","properties":{"auditEventsSelection":{"description":"What audit log data should be included in the report. If not specified, the report will contain no audit log data. The selection may be further filtered by the Report.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuditEventsSelection"},"downloadTemplates":{"description":"The set of templates used to render the report for downloads.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTemplate"}},"includeCISBenchmarkData":{"description":"Whether to include the full cis benchmark test results in the report.","type":"boolean"},"includeEndpointData":{"description":"Whether to include endpoint data in the report. The actual endpoints included may be filtered by the Report, but will otherwise contain the full set of endpoints.","type":"boolean"},"includeEndpointFlowLogData":{"description":"Whether to include endpoint-to-endpoint flow log data in the report.","type":"boolean"},"uiSummaryTemplate":{"description":"The summary template, explicitly used by the UI to render a summary version of the report. This should render to json containing a sets of widgets that the UI can use to render the summary. The rendered data is returned on the list query of the reports.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTemplate"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.RouteTableRange":{"type":"object","required":["min","max"],"properties":{"max":{"type":"integer","format":"int32"},"min":{"type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.Rule":{"description":"A Rule encapsulates a set of match criteria and an action. Both selector-based security Policy and security Profiles reference rules - separated out as a list of rules for both ingress and egress packet matching.\n\nEach positive match criteria has a negated version, prefixed with \"Not\". All the match criteria within a rule must be satisfied for a packet to match. A single rule can contain the positive and negative version of a match and both must be satisfied for the rule to match.","type":"object","required":["action"],"properties":{"action":{"type":"string"},"destination":{"description":"Destination contains the match criteria that apply to destination entity.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EntityRule"},"http":{"description":"HTTP contains match criteria that apply to HTTP requests.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPMatch"},"icmp":{"description":"ICMP is an optional field that restricts the rule to apply to a specific type and code of ICMP traffic. This should only be specified if the Protocol field is set to \"ICMP\" or \"ICMPv6\".","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ICMPFields"},"ipVersion":{"description":"IPVersion is an optional field that restricts the rule to only match a specific IP version.","type":"integer","format":"int32"},"metadata":{"description":"Metadata contains additional information for this rule","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.RuleMetadata"},"notICMP":{"description":"NotICMP is the negated version of the ICMP field.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ICMPFields"},"notProtocol":{"description":"NotProtocol is the negated version of the Protocol field.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Protocol"},"protocol":{"description":"Protocol is an optional field that restricts the rule to only apply to traffic of a specific IP protocol. Required if any of the EntityRules contain Ports (because ports only apply to certain protocols).\n\nMust be one of these string values: \"TCP\", \"UDP\", \"ICMP\", \"ICMPv6\", \"SCTP\", \"UDPLite\" or an integer in the range 1-255.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Protocol"},"source":{"description":"Source contains the match criteria that apply to source entity.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EntityRule"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.RuleMetadata":{"type":"object","properties":{"annotations":{"description":"Annotations is a set of key value pairs that give extra information about the rule","type":"object","additionalProperties":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountControllerConfig":{"description":"ServiceAccountControllerConfig configures the service account controller, which syncs Kubernetes service accounts to Calico profiles (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountMatch":{"type":"object","properties":{"names":{"description":"Names is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) a pod running as a service account whose name is in the list.","type":"array","items":{"type":"string"}},"selector":{"description":"Selector is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) a pod running as a service account that matches the given label selector. If both Names and Selector are specified then they are AND'ed.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceClusterIPBlock":{"description":"ServiceClusterIPBlock represents a single allowed ClusterIP CIDR block.","type":"object","properties":{"cidr":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceExternalIPBlock":{"description":"ServiceExternalIPBlock represents a single allowed External IP CIDR block.","type":"object","properties":{"cidr":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceLoadBalancerIPBlock":{"description":"ServiceLoadBalancerIPBlock represents a single allowed LoadBalancer IP CIDR block.","type":"object","properties":{"cidr":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.StagedGlobalNetworkPolicySpec":{"type":"object","properties":{"applyOnForward":{"description":"ApplyOnForward indicates to apply the rules in this policy on forward traffic.","type":"boolean"},"doNotTrack":{"description":"DoNotTrack indicates whether packets matched by the rules in this policy should go through the data plane's connection tracking, such as Linux conntrack. If True, the rules in this policy are applied before any data plane connection tracking, and packets allowed by this policy are marked as not to be tracked.","type":"boolean"},"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"namespaceSelector":{"description":"NamespaceSelector is an optional field for an expression used to select a pod based on namespaces.","type":"string"},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"preDNAT":{"description":"PreDNAT indicates to apply the rules in this policy before any DNAT.","type":"boolean"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"stagedAction":{"description":"The staged action. If this is omitted, the default is Set.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress rules are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.StagedKubernetesNetworkPolicySpec":{"type":"object","properties":{"egress":{"description":"List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyEgressRule"}},"ingress":{"description":"List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyIngressRule"}},"podSelector":{"description":"Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector"},"policyTypes":{"description":"List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ \"Egress\" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include \"Egress\" (since such a policy would not include an Egress section and would otherwise default to just [ \"Ingress\" ]). This field is beta-level in 1.8","type":"array","items":{"type":"string"}},"stagedAction":{"description":"The staged action. If this is omitted, the default is Set.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.StagedNetworkPolicySpec":{"type":"object","properties":{"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"stagedAction":{"description":"The staged action. If this is omitted, the default is Set.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormat":{"type":"object","properties":{"csv":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatCSV"},"json":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatJSON"},"newlineDelimited":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatNewlineDelimited"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatCSV":{"type":"object","properties":{"columnDelimiter":{"type":"string"},"commentDelimiter":{"type":"string"},"disableRecordSizeValidation":{"type":"boolean"},"fieldName":{"type":"string"},"fieldNum":{"type":"integer","format":"int32"},"header":{"type":"boolean"},"recordSize":{"type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatJSON":{"type":"object","properties":{"path":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatNewlineDelimited":{"type":"object"},"com.github.projectcalico.libcalico-go.lib.apis.v3.TierSpec":{"description":"TierSpec contains the specification for a security policy tier resource.","type":"object","properties":{"order":{"description":"Order is an optional field that specifies the order in which the tier is applied. Tiers with higher \"order\" are applied after those with lower order. If the order is omitted, it may be considered to be \"infinite\" - i.e. the tier will be applied last. Tiers with identical order will be applied in alphanumerical order based on the Tier \"Name\".","type":"number","format":"double"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.WorkloadEndpointControllerConfig":{"description":"WorkloadEndpointControllerConfig configures the workload endpoint controller, which syncs Kubernetes labels to Calico workload endpoints (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.numorstring.Port":{"type":"string","format":"int-or-string"},"com.github.projectcalico.libcalico-go.lib.numorstring.Protocol":{"type":"string","format":"int-or-string"},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthenticationReviewStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"AuthenticationReview","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"AuthorizationReview","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.BGPConfigurationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfigurationList":{"description":"BGPConfigurationList is a list of BGPConfiguration resources.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPeerSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPPeer","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeerList":{"description":"BGPPeerList is a list of BGPPeer resources.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPPeerList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ClusterInformationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ClusterInformation","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformationList":{"description":"ClusterInformationList is a list of ClusterInformation objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ClusterInformationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.FelixConfigurationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"FelixConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfigurationList":{"description":"FelixConfigurationList contains a list of FelixConfiguration object.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"FelixConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlert","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertList":{"description":"GlobalAlertList is a list of GlobalAlert objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlertList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlertTemplate","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplateList":{"description":"GlobalAlertTemplateList is a list of GlobalAlertTemplate objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlertTemplateList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicyList":{"description":"GlobalNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkSet","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSetList":{"description":"GlobalNetworkSetList is a list of NetworkSet objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkSetList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReport","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportList":{"description":"GlobalReportList is a list of GlobalReport objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReportList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTypeSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReportType","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportTypeList":{"description":"GlobalReportTypeList is a list of GlobalReportType objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReportTypeList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalThreatFeed","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeedList":{"description":"GlobalThreatFeedList is a list of GlobalThreatFeed objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalThreatFeedList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HostEndpointSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"HostEndpoint","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpointList":{"description":"HostEndpointList is a list of HostEndpoint objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"HostEndpointList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.IPPoolSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"IPPool","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPoolList":{"description":"IPPoolList contains a list of IPPool resources.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"IPPoolList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"KubeControllersConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfigurationList":{"description":"KubeControllersConfigurationList contains a list of KubeControllersConfiguration object.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"KubeControllersConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeySpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeyStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"LicenseKey","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKeyList":{"description":"LicenseKeyList is a list of license objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"LicenseKeyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ManagedCluster","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedClusterList":{"description":"ManagedClusterList is a list of ManagedCluster objects (used for multi-cluster management).","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ManagedClusterList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicyList":{"description":"NetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkSetSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkSet","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSetList":{"description":"NetworkSetList is a list of NetworkSet objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkSetList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.PacketCaptureSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"PacketCapture","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCaptureList":{"description":"PacketCaptureList is a list of PacketCapture objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"PacketCaptureList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ProfileSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"Profile","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ProfileList":{"description":"ProfileList is a list of Profile objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ProfileList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.RemoteClusterConfigurationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"RemoteClusterConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfigurationList":{"description":"RemoteClusterConfigurationList is a list of RemoteClusterConfiguration objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"RemoteClusterConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.StagedGlobalNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedGlobalNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicyList":{"description":"StagedGlobalNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedGlobalNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.StagedKubernetesNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedKubernetesNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicyList":{"description":"StagedKubernetesNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedKubernetesNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.StagedNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicyList":{"description":"StagedNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.TierSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"Tier","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.TierList":{"description":"TierList is a list of Tier objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"TierList","version":"v3"}]},"io.k8s.api.core.v1.ConfigMapKeySelector":{"description":"Selects a key from a ConfigMap.","type":"object","required":["key"],"properties":{"key":{"description":"The key to select.","type":"string"},"name":{"description":"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names","type":"string"},"optional":{"description":"Specify whether the ConfigMap or its key must be defined","type":"boolean"}}},"io.k8s.api.core.v1.ObjectReference":{"description":"ObjectReference contains enough information to let you inspect or modify the referred object.","type":"object","properties":{"apiVersion":{"description":"API version of the referent.","type":"string"},"fieldPath":{"description":"If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: \"spec.containers{name}\" (where \"name\" refers to the name of the container that triggered the event) or if no container name is specified \"spec.containers[2]\" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.","type":"string"},"kind":{"description":"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names","type":"string"},"namespace":{"description":"Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/","type":"string"},"resourceVersion":{"description":"Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency","type":"string"},"uid":{"description":"UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids","type":"string"}}},"io.k8s.api.core.v1.SecretKeySelector":{"description":"SecretKeySelector selects a key of a Secret.","type":"object","required":["key"],"properties":{"key":{"description":"The key of the secret to select from. Must be a valid secret key.","type":"string"},"name":{"description":"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names","type":"string"},"optional":{"description":"Specify whether the Secret or its key must be defined","type":"boolean"}}},"io.k8s.api.networking.v1.IPBlock":{"description":"IPBlock describes a particular CIDR (Ex. \"192.168.1.1/24\",\"2001:db9::/64\") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.","type":"object","required":["cidr"],"properties":{"cidr":{"description":"CIDR is a string representing the IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\"","type":"string"},"except":{"description":"Except is a slice of CIDRs that should not be included within an IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\" Except values will be rejected if they are outside the CIDR range","type":"array","items":{"type":"string"}}}},"io.k8s.api.networking.v1.NetworkPolicyEgressRule":{"description":"NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8","type":"object","properties":{"ports":{"description":"List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPort"}},"to":{"description":"List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPeer"}}}},"io.k8s.api.networking.v1.NetworkPolicyIngressRule":{"description":"NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.","type":"object","properties":{"from":{"description":"List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the from list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPeer"}},"ports":{"description":"List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPort"}}}},"io.k8s.api.networking.v1.NetworkPolicyPeer":{"description":"NetworkPolicyPeer describes a peer to allow traffic to/from. Only certain combinations of fields are allowed","type":"object","properties":{"ipBlock":{"description":"IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.","$ref":"#/definitions/io.k8s.api.networking.v1.IPBlock"},"namespaceSelector":{"description":"Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.\n\nIf PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector"},"podSelector":{"description":"This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.\n\nIf NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy's own Namespace.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector"}}},"io.k8s.api.networking.v1.NetworkPolicyPort":{"description":"NetworkPolicyPort describes a port to allow traffic on","type":"object","properties":{"port":{"description":"The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers.","$ref":"#/definitions/io.k8s.apimachinery.pkg.util.intstr.IntOrString"},"protocol":{"description":"The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup":{"description":"APIGroup contains the name, the supported versions, and the preferred version of a group.","type":"object","required":["name","versions"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"name is the name of the group.","type":"string"},"preferredVersion":{"description":"preferredVersion is the version preferred by the API server, which probably is the storage version.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.GroupVersionForDiscovery"},"serverAddressByClientCIDRs":{"description":"a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ServerAddressByClientCIDR"}},"versions":{"description":"versions are the versions supported in this group.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.GroupVersionForDiscovery"}}},"x-kubernetes-group-version-kind":[{"group":"","kind":"APIGroup","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.APIGroupList":{"description":"APIGroupList is a list of APIGroup, to allow clients to discover the API at /apis.","type":"object","required":["groups"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"groups":{"description":"groups is a list of APIGroup.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"APIGroupList","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.APIResource":{"description":"APIResource specifies the name of a resource and whether it is namespaced.","type":"object","required":["name","singularName","namespaced","kind","verbs"],"properties":{"categories":{"description":"categories is a list of the grouped resources this resource belongs to (e.g. 'all')","type":"array","items":{"type":"string"}},"group":{"description":"group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale\".","type":"string"},"kind":{"description":"kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')","type":"string"},"name":{"description":"name is the plural name of the resource.","type":"string"},"namespaced":{"description":"namespaced indicates if a resource is namespaced or not.","type":"boolean"},"shortNames":{"description":"shortNames is a list of suggested short names of the resource.","type":"array","items":{"type":"string"}},"singularName":{"description":"singularName is the singular name of the resource. This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.","type":"string"},"storageVersionHash":{"description":"The hash value of the storage version, the version this resource is converted to when written to the data store. Value must be treated as opaque by clients. Only equality comparison on the value is valid. This is an alpha feature and may change or be removed in the future. The field is populated by the apiserver only if the StorageVersionHash feature gate is enabled. This field will remain optional even if it graduates.","type":"string"},"verbs":{"description":"verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)","type":"array","items":{"type":"string"}},"version":{"description":"version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource's group)\".","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList":{"description":"APIResourceList is a list of APIResource, it is used to expose the name of the resources supported in a specific group and version, and if the resource is namespaced.","type":"object","required":["groupVersion","resources"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"groupVersion":{"description":"groupVersion is the group and version this APIResourceList is for.","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"resources":{"description":"resources contains the name of the resources and if they are namespaced.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResource"}}},"x-kubernetes-group-version-kind":[{"group":"","kind":"APIResourceList","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions":{"description":"DeleteOptions may be provided when deleting an API object.","type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"dryRun":{"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","type":"array","items":{"type":"string"}},"gracePeriodSeconds":{"description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","type":"integer","format":"int64"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"orphanDependents":{"description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","type":"boolean"},"preconditions":{"description":"Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Preconditions"},"propagationPolicy":{"description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"DeleteOptions","version":"v1"},{"group":"projectcalico.org","kind":"DeleteOptions","version":"v3"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.Duration":{"description":"Duration is a wrapper around time.Duration which supports correct marshaling to YAML and JSON. In particular, it marshals into strings, which can be used as map keys in json.","type":"string"},"io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1":{"description":"FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format.\n\nEach key is either a '.' representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: 'f:\u003cname\u003e', where \u003cname\u003e is the name of a field in a struct, or key in a map 'v:\u003cvalue\u003e', where \u003cvalue\u003e is the exact json formatted value of a list item 'i:\u003cindex\u003e', where \u003cindex\u003e is position of a item in a list 'k:\u003ckeys\u003e', where \u003ckeys\u003e is a map of a list item's key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set.\n\nThe exact format is defined in sigs.k8s.io/structured-merge-diff","type":"object"},"io.k8s.apimachinery.pkg.apis.meta.v1.GroupVersionForDiscovery":{"description":"GroupVersion contains the \"group/version\" and \"version\" string of a version. It is made a struct to keep extensibility.","type":"object","required":["groupVersion","version"],"properties":{"groupVersion":{"description":"groupVersion specifies the API group and version in the form \"group/version\"","type":"string"},"version":{"description":"version specifies the version in the form of \"version\". This is to save the clients the trouble of splitting the GroupVersion.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector":{"description":"A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.","type":"object","properties":{"matchExpressions":{"description":"matchExpressions is a list of label selector requirements. The requirements are ANDed.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelectorRequirement"}},"matchLabels":{"description":"matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is \"key\", the operator is \"In\", and the values array contains only \"value\". The requirements are ANDed.","type":"object","additionalProperties":{"type":"string"}}}},"io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelectorRequirement":{"description":"A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.","type":"object","required":["key","operator"],"properties":{"key":{"description":"key is the label key that the selector applies to.","type":"string","x-kubernetes-patch-merge-key":"key","x-kubernetes-patch-strategy":"merge"},"operator":{"description":"operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.","type":"string"},"values":{"description":"values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.","type":"array","items":{"type":"string"}}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta":{"description":"ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.","type":"object","properties":{"continue":{"description":"continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a consistent list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response, unless you have received this token from an error message.","type":"string"},"remainingItemCount":{"description":"remainingItemCount is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the field will be left unset and omitted during serialization. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and this field will be left unset and omitted during serialization. Servers older than v1.15 do not set this field. The intended use of the remainingItemCount is *estimating* the size of a collection. Clients should not rely on the remainingItemCount to be set or to be exact.","type":"integer","format":"int64"},"resourceVersion":{"description":"String that identifies the server's internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency","type":"string"},"selfLink":{"description":"selfLink is a URL representing this object. Populated by the system. Read-only.\n\nDEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ManagedFieldsEntry":{"description":"ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.","type":"object","properties":{"apiVersion":{"description":"APIVersion defines the version of this resource that this field set applies to. The format is \"group/version\" just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted.","type":"string"},"fieldsType":{"description":"FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: \"FieldsV1\"","type":"string"},"fieldsV1":{"description":"FieldsV1 holds the first JSON version format as described in the \"FieldsV1\" type.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1"},"manager":{"description":"Manager is an identifier of the workflow managing these fields.","type":"string"},"operation":{"description":"Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are 'Apply' and 'Update'.","type":"string"},"time":{"description":"Time is timestamp of when these fields were set. It should always be empty if Operation is 'Apply'","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta":{"description":"ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.","type":"object","properties":{"annotations":{"description":"Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations","type":"object","additionalProperties":{"type":"string"}},"clusterName":{"description":"The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.","type":"string"},"creationTimestamp":{"description":"CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.\n\nPopulated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"deletionGracePeriodSeconds":{"description":"Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.","type":"integer","format":"int64"},"deletionTimestamp":{"description":"DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested.\n\nPopulated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"finalizers":{"description":"Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed. Finalizers may be processed and removed in any order. Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list.","type":"array","items":{"type":"string"},"x-kubernetes-patch-strategy":"merge"},"generateName":{"description":"GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server.\n\nIf this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).\n\nApplied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency","type":"string"},"generation":{"description":"A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.","type":"integer","format":"int64"},"labels":{"description":"Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels","type":"object","additionalProperties":{"type":"string"}},"managedFields":{"description":"ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like \"ci-cd\". The set of fields is always in the version that the workflow used when modifying the object.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ManagedFieldsEntry"}},"name":{"description":"Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names","type":"string"},"namespace":{"description":"Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the \"default\" namespace, but \"default\" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty.\n\nMust be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces","type":"string"},"ownerReferences":{"description":"List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.OwnerReference"},"x-kubernetes-patch-merge-key":"uid","x-kubernetes-patch-strategy":"merge"},"resourceVersion":{"description":"An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources.\n\nPopulated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency","type":"string"},"selfLink":{"description":"SelfLink is a URL representing this object. Populated by the system. Read-only.\n\nDEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.","type":"string"},"uid":{"description":"UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations.\n\nPopulated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.OwnerReference":{"description":"OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.","type":"object","required":["apiVersion","kind","name","uid"],"properties":{"apiVersion":{"description":"API version of the referent.","type":"string"},"blockOwnerDeletion":{"description":"If true, AND if the owner has the \"foregroundDeletion\" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs \"delete\" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.","type":"boolean"},"controller":{"description":"If true, this reference points to the managing controller.","type":"boolean"},"kind":{"description":"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names","type":"string"},"uid":{"description":"UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.Patch":{"description":"Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.","type":"object"},"io.k8s.apimachinery.pkg.apis.meta.v1.Preconditions":{"description":"Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.","type":"object","properties":{"resourceVersion":{"description":"Specifies the target ResourceVersion","type":"string"},"uid":{"description":"Specifies the target UID.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ServerAddressByClientCIDR":{"description":"ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.","type":"object","required":["clientCIDR","serverAddress"],"properties":{"clientCIDR":{"description":"The CIDR with which clients can match their IP to figure out the server address that they should use.","type":"string"},"serverAddress":{"description":"Address of this server, suitable for a client that matches the above CIDR. This can be a hostname, hostname:port, IP or IP:port.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.Status":{"description":"Status is a return value for calls that don't return other objects.","type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"code":{"description":"Suggested HTTP return code for this status, 0 if not set.","type":"integer","format":"int32"},"details":{"description":"Extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.StatusDetails"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"message":{"description":"A human-readable description of the status of this operation.","type":"string"},"metadata":{"description":"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"},"reason":{"description":"A machine-readable description of why this operation is in the \"Failure\" status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.","type":"string"},"status":{"description":"Status of the operation. One of: \"Success\" or \"Failure\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status","type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"Status","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.StatusCause":{"description":"StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.","type":"object","properties":{"field":{"description":"The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed. Fields may appear more than once in an array of causes due to fields having multiple errors. Optional.\n\nExamples:\n \"name\" - the field \"name\" on the current resource\n \"items[0].name\" - the field \"name\" on the first array entry in \"items\"","type":"string"},"message":{"description":"A human-readable description of the cause of the error. This field may be presented as-is to a reader.","type":"string"},"reason":{"description":"A machine-readable description of the cause of the error. If this value is empty there is no information available.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.StatusDetails":{"description":"StatusDetails is a set of additional properties that MAY be set by the server to provide additional information about a response. The Reason field of a Status object defines what attributes will be set. Clients must ignore fields that do not match the defined type of each attribute, and should assume that any attribute may be empty, invalid, or under defined.","type":"object","properties":{"causes":{"description":"The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.StatusCause"}},"group":{"description":"The group attribute of the resource associated with the status StatusReason.","type":"string"},"kind":{"description":"The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).","type":"string"},"retryAfterSeconds":{"description":"If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.","type":"integer","format":"int32"},"uid":{"description":"UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.Time":{"description":"Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON. Wrappers are provided for many of the factory methods that the time package offers.","type":"string","format":"date-time"},"io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent":{"description":"Event represents a single event to a watched resource.","type":"object","required":["type","object"],"properties":{"object":{"description":"Object is:\n * If Type is Added or Modified: the new state of the object.\n * If Type is Deleted: the state of the object immediately before deletion.\n * If Type is Error: *Status is recommended; other types may make sense\n depending on context.","$ref":"#/definitions/io.k8s.apimachinery.pkg.runtime.RawExtension"},"type":{"type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"WatchEvent","version":"v1"},{"group":"projectcalico.org","kind":"WatchEvent","version":"v3"}]},"io.k8s.apimachinery.pkg.runtime.RawExtension":{"description":"RawExtension is used to hold extensions in external versions.\n\nTo use this, make a field which has RawExtension as its type in your external, versioned struct, and Object in your internal struct. You also need to register your various plugin types.\n\n// Internal package: type MyAPIObject struct {\n\truntime.TypeMeta `json:\",inline\"`\n\tMyPlugin runtime.Object `json:\"myPlugin\"`\n} type PluginA struct {\n\tAOption string `json:\"aOption\"`\n}\n\n// External package: type MyAPIObject struct {\n\truntime.TypeMeta `json:\",inline\"`\n\tMyPlugin runtime.RawExtension `json:\"myPlugin\"`\n} type PluginA struct {\n\tAOption string `json:\"aOption\"`\n}\n\n// On the wire, the JSON will look something like this: {\n\t\"kind\":\"MyAPIObject\",\n\t\"apiVersion\":\"v1\",\n\t\"myPlugin\": {\n\t\t\"kind\":\"PluginA\",\n\t\t\"aOption\":\"foo\",\n\t},\n}\n\nSo what happens? Decode first uses json or yaml to unmarshal the serialized data into your external MyAPIObject. That causes the raw JSON to be stored, but not unpacked. The next step is to copy (using pkg/conversion) into the internal struct. The runtime package's DefaultScheme has conversion functions installed which will unpack the JSON stored in RawExtension, turning it into the correct object type, and storing it in the Object. (TODO: In the case where the object is of an unknown type, a runtime.Unknown object will be created and stored.)","type":"object"},"io.k8s.apimachinery.pkg.util.intstr.IntOrString":{"description":"IntOrString is a type that can hold an int32 or a string. When used in JSON or YAML marshalling and unmarshalling, it produces or consumes the inner type. This allows you to have, for example, a JSON field that can accept a name or number.","type":"string","format":"int-or-string"},"io.k8s.apimachinery.pkg.version.Info":{"description":"Info contains versioning information. how we'll want to distribute that information.","type":"object","required":["major","minor","gitVersion","gitCommit","gitTreeState","buildDate","goVersion","compiler","platform"],"properties":{"buildDate":{"type":"string"},"compiler":{"type":"string"},"gitCommit":{"type":"string"},"gitTreeState":{"type":"string"},"gitVersion":{"type":"string"},"goVersion":{"type":"string"},"major":{"type":"string"},"minor":{"type":"string"},"platform":{"type":"string"}}}}} \ No newline at end of file +{"swagger":"2.0","info":{"title":"Generic API Server","version":"unversioned"},"paths":{"/apis/":{"get":{"description":"get available API versions","consumes":["application/json","application/yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["apis"],"operationId":"getAPIVersions","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIGroupList"}}}}},"/apis/projectcalico.org/":{"get":{"description":"get information of a group","consumes":["application/json","application/yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg"],"operationId":"getProjectcalicoOrgAPIGroup","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup"}}}}},"/apis/projectcalico.org/v3/":{"get":{"description":"get available resources","consumes":["application/json","application/yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"getProjectcalicoOrgV3APIResources","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList"}}}}},"/apis/projectcalico.org/v3/authenticationreviews":{"post":{"description":"create an AuthenticationReview","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3AuthenticationReview","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthenticationReview"}},"parameters":[{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/authorizationreviews":{"post":{"description":"create an AuthorizationReview","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3AuthorizationReview","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthorizationReview"}},"parameters":[{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgpconfigurations":{"get":{"description":"list or watch objects of kind BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3BGPConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"post":{"description":"create a BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"delete":{"description":"delete collection of BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionBGPConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgpconfigurations/{name}":{"get":{"description":"read the specified BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3BGPConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"put":{"description":"replace the specified BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"delete":{"description":"delete a BGPConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"patch":{"description":"partially update the specified BGPConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3BGPConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the BGPConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgppeers":{"get":{"description":"list or watch objects of kind BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3BGPPeer","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeerList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"post":{"description":"create a BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"delete":{"description":"delete collection of BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionBGPPeer","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/bgppeers/{name}":{"get":{"description":"read the specified BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3BGPPeer","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"put":{"description":"replace the specified BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"delete":{"description":"delete a BGPPeer","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"patch":{"description":"partially update the specified BGPPeer","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3BGPPeer","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the BGPPeer","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/clusterinformations":{"get":{"description":"list or watch objects of kind ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3ClusterInformation","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"post":{"description":"create a ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"delete":{"description":"delete collection of ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionClusterInformation","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/clusterinformations/{name}":{"get":{"description":"read the specified ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3ClusterInformation","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"put":{"description":"replace the specified ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"delete":{"description":"delete a ClusterInformation","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"patch":{"description":"partially update the specified ClusterInformation","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3ClusterInformation","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the ClusterInformation","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/felixconfigurations":{"get":{"description":"list or watch objects of kind FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3FelixConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"post":{"description":"create a FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"delete":{"description":"delete collection of FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionFelixConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/felixconfigurations/{name}":{"get":{"description":"read the specified FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3FelixConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"put":{"description":"replace the specified FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"delete":{"description":"delete a FelixConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"patch":{"description":"partially update the specified FelixConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3FelixConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the FelixConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerts":{"get":{"description":"list or watch objects of kind GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalAlert","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"post":{"description":"create a GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"delete":{"description":"delete collection of GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalAlert","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerts/{name}":{"get":{"description":"read the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalAlert","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"put":{"description":"replace the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"delete":{"description":"delete a GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"patch":{"description":"partially update the specified GlobalAlert","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalAlert","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalAlert","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerts/{name}/status":{"get":{"description":"read status of the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalAlertStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"put":{"description":"replace status of the specified GlobalAlert","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalAlertStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"patch":{"description":"partially update status of the specified GlobalAlert","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalAlertStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalAlert","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerttemplates":{"get":{"description":"list or watch objects of kind GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplateList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"post":{"description":"create a GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"delete":{"description":"delete collection of GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalAlertTemplate","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalalerttemplates/{name}":{"get":{"description":"read the specified GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"put":{"description":"replace the specified GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"delete":{"description":"delete a GlobalAlertTemplate","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"patch":{"description":"partially update the specified GlobalAlertTemplate","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalAlertTemplate","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalAlertTemplate","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworkpolicies":{"get":{"description":"list or watch objects of kind GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"post":{"description":"create a GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"delete":{"description":"delete collection of GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworkpolicies/{name}":{"get":{"description":"read the specified GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"put":{"description":"replace the specified GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"delete":{"description":"delete a GlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"patch":{"description":"partially update the specified GlobalNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworksets":{"get":{"description":"list or watch objects of kind GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSetList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"post":{"description":"create a GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"delete":{"description":"delete collection of GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalnetworksets/{name}":{"get":{"description":"read the specified GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"put":{"description":"replace the specified GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"delete":{"description":"delete a GlobalNetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"patch":{"description":"partially update the specified GlobalNetworkSet","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreports":{"get":{"description":"list or watch objects of kind GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalReport","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"post":{"description":"create a GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"delete":{"description":"delete collection of GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalReport","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreports/{name}":{"get":{"description":"read the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalReport","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"put":{"description":"replace the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"delete":{"description":"delete a GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"patch":{"description":"partially update the specified GlobalReport","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalReport","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalReport","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreports/{name}/status":{"get":{"description":"read status of the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalReportStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"put":{"description":"replace status of the specified GlobalReport","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalReportStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"patch":{"description":"partially update status of the specified GlobalReport","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalReportStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalReport","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreporttypes":{"get":{"description":"list or watch objects of kind GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalReportType","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportTypeList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"post":{"description":"create a GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"delete":{"description":"delete collection of GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalReportType","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalreporttypes/{name}":{"get":{"description":"read the specified GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalReportType","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"put":{"description":"replace the specified GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"delete":{"description":"delete a GlobalReportType","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"patch":{"description":"partially update the specified GlobalReportType","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalReportType","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalReportType","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalthreatfeeds":{"get":{"description":"list or watch objects of kind GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeedList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"post":{"description":"create a GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"delete":{"description":"delete collection of GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionGlobalThreatFeed","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalthreatfeeds/{name}":{"get":{"description":"read the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"put":{"description":"replace the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"delete":{"description":"delete a GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"patch":{"description":"partially update the specified GlobalThreatFeed","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalThreatFeed","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalThreatFeed","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/globalthreatfeeds/{name}/status":{"get":{"description":"read status of the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3GlobalThreatFeedStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"put":{"description":"replace status of the specified GlobalThreatFeed","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3GlobalThreatFeedStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"patch":{"description":"partially update status of the specified GlobalThreatFeed","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3GlobalThreatFeedStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the GlobalThreatFeed","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/hostendpoints":{"get":{"description":"list or watch objects of kind HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3HostEndpoint","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpointList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"post":{"description":"create a HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"delete":{"description":"delete collection of HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionHostEndpoint","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/hostendpoints/{name}":{"get":{"description":"read the specified HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3HostEndpoint","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"put":{"description":"replace the specified HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"delete":{"description":"delete a HostEndpoint","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"patch":{"description":"partially update the specified HostEndpoint","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3HostEndpoint","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the HostEndpoint","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/ippools":{"get":{"description":"list or watch objects of kind IPPool","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3IPPool","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPoolList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"post":{"description":"create an IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"delete":{"description":"delete collection of IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionIPPool","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/ippools/{name}":{"get":{"description":"read the specified IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3IPPool","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"put":{"description":"replace the specified IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"delete":{"description":"delete an IPPool","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"patch":{"description":"partially update the specified IPPool","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3IPPool","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the IPPool","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/kubecontrollersconfigurations":{"get":{"description":"list or watch objects of kind KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"post":{"description":"create a KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"delete":{"description":"delete collection of KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionKubeControllersConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/kubecontrollersconfigurations/{name}":{"get":{"description":"read the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"put":{"description":"replace the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"delete":{"description":"delete a KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"patch":{"description":"partially update the specified KubeControllersConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3KubeControllersConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the KubeControllersConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/kubecontrollersconfigurations/{name}/status":{"get":{"description":"read status of the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3KubeControllersConfigurationStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"put":{"description":"replace status of the specified KubeControllersConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3KubeControllersConfigurationStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"patch":{"description":"partially update status of the specified KubeControllersConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3KubeControllersConfigurationStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the KubeControllersConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/licensekeys":{"get":{"description":"list or watch objects of kind LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3LicenseKey","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKeyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"post":{"description":"create a LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"delete":{"description":"delete collection of LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionLicenseKey","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/licensekeys/{name}":{"get":{"description":"read the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3LicenseKey","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"put":{"description":"replace the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"delete":{"description":"delete a LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"patch":{"description":"partially update the specified LicenseKey","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3LicenseKey","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the LicenseKey","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/licensekeys/{name}/status":{"get":{"description":"read status of the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3LicenseKeyStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"put":{"description":"replace status of the specified LicenseKey","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3LicenseKeyStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"patch":{"description":"partially update status of the specified LicenseKey","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3LicenseKeyStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the LicenseKey","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/managedclusters":{"get":{"description":"list or watch objects of kind ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3ManagedCluster","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedClusterList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"post":{"description":"create a ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"delete":{"description":"delete collection of ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionManagedCluster","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/managedclusters/{name}":{"get":{"description":"read the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3ManagedCluster","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"put":{"description":"replace the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"delete":{"description":"delete a ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"patch":{"description":"partially update the specified ManagedCluster","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3ManagedCluster","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the ManagedCluster","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/managedclusters/{name}/status":{"get":{"description":"read status of the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3ManagedClusterStatus","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"put":{"description":"replace status of the specified ManagedCluster","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3ManagedClusterStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"patch":{"description":"partially update status of the specified ManagedCluster","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3ManagedClusterStatus","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the ManagedCluster","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networkpolicies":{"get":{"description":"list or watch objects of kind NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"post":{"description":"create a NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"delete":{"description":"delete collection of NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networkpolicies/{name}":{"get":{"description":"read the specified NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"put":{"description":"replace the specified NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"delete":{"description":"delete a NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"patch":{"description":"partially update the specified NetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the NetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networksets":{"get":{"description":"list or watch objects of kind NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSetList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"post":{"description":"create a NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"delete":{"description":"delete collection of NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/networksets/{name}":{"get":{"description":"read the specified NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"put":{"description":"replace the specified NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"delete":{"description":"delete a NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"patch":{"description":"partially update the specified NetworkSet","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedNetworkSet","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the NetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/packetcaptures":{"get":{"description":"list or watch objects of kind PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCaptureList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"post":{"description":"create a PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"delete":{"description":"delete collection of PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedPacketCapture","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/packetcaptures/{name}":{"get":{"description":"read the specified PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"put":{"description":"replace the specified PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"delete":{"description":"delete a PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"patch":{"description":"partially update the specified PacketCapture","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedPacketCapture","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the PacketCapture","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagedkubernetesnetworkpolicies":{"get":{"description":"list or watch objects of kind StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"post":{"description":"create a StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"delete":{"description":"delete collection of StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagedkubernetesnetworkpolicies/{name}":{"get":{"description":"read the specified StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"put":{"description":"replace the specified StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"delete":{"description":"delete a StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"patch":{"description":"partially update the specified StagedKubernetesNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the StagedKubernetesNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagednetworkpolicies":{"get":{"description":"list or watch objects of kind StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"post":{"description":"create a StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"delete":{"description":"delete collection of StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionNamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/namespaces/{namespace}/stagednetworkpolicies/{name}":{"get":{"description":"read the specified StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"put":{"description":"replace the specified StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"delete":{"description":"delete a StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"patch":{"description":"partially update the specified StagedNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3NamespacedStagedNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the StagedNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/networkpolicies":{"get":{"description":"list or watch objects of kind NetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NetworkPolicyForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/networksets":{"get":{"description":"list or watch objects of kind NetworkSet","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3NetworkSetForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSetList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/packetcaptures":{"get":{"description":"list or watch objects of kind PacketCapture","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3PacketCaptureForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCaptureList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/profiles":{"get":{"description":"list or watch objects of kind Profile","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3Profile","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ProfileList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"post":{"description":"create a Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"delete":{"description":"delete collection of Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionProfile","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/profiles/{name}":{"get":{"description":"read the specified Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3Profile","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"put":{"description":"replace the specified Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"delete":{"description":"delete a Profile","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"patch":{"description":"partially update the specified Profile","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3Profile","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the Profile","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/remoteclusterconfigurations":{"get":{"description":"list or watch objects of kind RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfigurationList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"post":{"description":"create a RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"delete":{"description":"delete collection of RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionRemoteClusterConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/remoteclusterconfigurations/{name}":{"get":{"description":"read the specified RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"put":{"description":"replace the specified RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"delete":{"description":"delete a RemoteClusterConfiguration","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"patch":{"description":"partially update the specified RemoteClusterConfiguration","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3RemoteClusterConfiguration","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the RemoteClusterConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/stagedglobalnetworkpolicies":{"get":{"description":"list or watch objects of kind StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"post":{"description":"create a StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"delete":{"description":"delete collection of StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionStagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/stagedglobalnetworkpolicies/{name}":{"get":{"description":"read the specified StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"put":{"description":"replace the specified StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"delete":{"description":"delete a StagedGlobalNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"patch":{"description":"partially update the specified StagedGlobalNetworkPolicy","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3StagedGlobalNetworkPolicy","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the StagedGlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/stagedkubernetesnetworkpolicies":{"get":{"description":"list or watch objects of kind StagedKubernetesNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3StagedKubernetesNetworkPolicyForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/stagednetworkpolicies":{"get":{"description":"list or watch objects of kind StagedNetworkPolicy","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3StagedNetworkPolicyForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicyList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/tiers":{"get":{"description":"list or watch objects of kind Tier","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"listProjectcalicoOrgV3Tier","parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.TierList"}}},"x-kubernetes-action":"list","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"post":{"description":"create a Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"createProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"post","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"delete":{"description":"delete collection of Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3CollectionTier","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"deletecollection","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/tiers/{name}":{"get":{"description":"read the specified Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"readProjectcalicoOrgV3Tier","parameters":[{"uniqueItems":true,"type":"boolean","description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'. Deprecated. Planned for removal in 1.18.","name":"exact","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Should this value be exported. Export strips fields that a user can not specify. Deprecated. Planned for removal in 1.18.","name":"export","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"get","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"put":{"description":"replace the specified Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"replaceProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.","name":"fieldManager","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"201":{"description":"Created","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"put","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"delete":{"description":"delete a Tier","consumes":["*/*"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"deleteProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"integer","description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","name":"gracePeriodSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","name":"orphanDependents","in":"query"},{"uniqueItems":true,"type":"string","description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","name":"propagationPolicy","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}},"202":{"description":"Accepted","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"}}},"x-kubernetes-action":"delete","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"patch":{"description":"partially update the specified Tier","consumes":["application/json-patch+json","application/merge-patch+json","application/strategic-merge-patch+json","application/apply-patch+yaml"],"produces":["application/json","application/yaml"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"patchProjectcalicoOrgV3Tier","parameters":[{"name":"body","in":"body","required":true,"schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"}},{"uniqueItems":true,"type":"string","description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","name":"dryRun","in":"query"},{"uniqueItems":true,"type":"string","description":"fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).","name":"fieldManager","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.","name":"force","in":"query"}],"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}}},"x-kubernetes-action":"patch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"string","description":"name of the Tier","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"}]},"/apis/projectcalico.org/v3/watch/authenticationreviews/{name}":{"get":{"description":"watch changes to an object of kind AuthenticationReview. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3AuthenticationReview","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthenticationReview"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the AuthenticationReview","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/authorizationreviews/{name}":{"get":{"description":"watch changes to an object of kind AuthorizationReview. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3AuthorizationReview","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"AuthorizationReview"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the AuthorizationReview","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgpconfigurations":{"get":{"description":"watch individual changes to a list of BGPConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgpconfigurations/{name}":{"get":{"description":"watch changes to an object of kind BGPConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the BGPConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgppeers":{"get":{"description":"watch individual changes to a list of BGPPeer. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPPeerList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/bgppeers/{name}":{"get":{"description":"watch changes to an object of kind BGPPeer. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3BGPPeer","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"BGPPeer"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the BGPPeer","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/clusterinformations":{"get":{"description":"watch individual changes to a list of ClusterInformation. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ClusterInformationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/clusterinformations/{name}":{"get":{"description":"watch changes to an object of kind ClusterInformation. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ClusterInformation","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ClusterInformation"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the ClusterInformation","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/felixconfigurations":{"get":{"description":"watch individual changes to a list of FelixConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3FelixConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/felixconfigurations/{name}":{"get":{"description":"watch changes to an object of kind FelixConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3FelixConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"FelixConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the FelixConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerts":{"get":{"description":"watch individual changes to a list of GlobalAlert. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlertList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerts/{name}":{"get":{"description":"watch changes to an object of kind GlobalAlert. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlert","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlert"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalAlert","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerttemplates":{"get":{"description":"watch individual changes to a list of GlobalAlertTemplate. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlertTemplateList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalalerttemplates/{name}":{"get":{"description":"watch changes to an object of kind GlobalAlertTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalAlertTemplate","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalAlertTemplate"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalAlertTemplate","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworkpolicies":{"get":{"description":"watch individual changes to a list of GlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind GlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworksets":{"get":{"description":"watch individual changes to a list of GlobalNetworkSet. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkSetList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalnetworksets/{name}":{"get":{"description":"watch changes to an object of kind GlobalNetworkSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalNetworkSet","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalNetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalNetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreports":{"get":{"description":"watch individual changes to a list of GlobalReport. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReportList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreports/{name}":{"get":{"description":"watch changes to an object of kind GlobalReport. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReport","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReport"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalReport","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreporttypes":{"get":{"description":"watch individual changes to a list of GlobalReportType. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReportTypeList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalreporttypes/{name}":{"get":{"description":"watch changes to an object of kind GlobalReportType. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalReportType","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalReportType"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalReportType","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalthreatfeeds":{"get":{"description":"watch individual changes to a list of GlobalThreatFeed. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalThreatFeedList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/globalthreatfeeds/{name}":{"get":{"description":"watch changes to an object of kind GlobalThreatFeed. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3GlobalThreatFeed","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"GlobalThreatFeed"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the GlobalThreatFeed","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/hostendpoints":{"get":{"description":"watch individual changes to a list of HostEndpoint. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3HostEndpointList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/hostendpoints/{name}":{"get":{"description":"watch changes to an object of kind HostEndpoint. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3HostEndpoint","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"HostEndpoint"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the HostEndpoint","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/ippools":{"get":{"description":"watch individual changes to a list of IPPool. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3IPPoolList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/ippools/{name}":{"get":{"description":"watch changes to an object of kind IPPool. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3IPPool","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"IPPool"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the IPPool","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/kubecontrollersconfigurations":{"get":{"description":"watch individual changes to a list of KubeControllersConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3KubeControllersConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/kubecontrollersconfigurations/{name}":{"get":{"description":"watch changes to an object of kind KubeControllersConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3KubeControllersConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"KubeControllersConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the KubeControllersConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/licensekeys":{"get":{"description":"watch individual changes to a list of LicenseKey. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3LicenseKeyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/licensekeys/{name}":{"get":{"description":"watch changes to an object of kind LicenseKey. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3LicenseKey","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"LicenseKey"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the LicenseKey","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/managedclusters":{"get":{"description":"watch individual changes to a list of ManagedCluster. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ManagedClusterList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/managedclusters/{name}":{"get":{"description":"watch changes to an object of kind ManagedCluster. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ManagedCluster","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"ManagedCluster"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the ManagedCluster","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networkpolicies":{"get":{"description":"watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networkpolicies/{name}":{"get":{"description":"watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the NetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networksets":{"get":{"description":"watch individual changes to a list of NetworkSet. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkSetList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/networksets/{name}":{"get":{"description":"watch changes to an object of kind NetworkSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedNetworkSet","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the NetworkSet","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/packetcaptures":{"get":{"description":"watch individual changes to a list of PacketCapture. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedPacketCaptureList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/packetcaptures/{name}":{"get":{"description":"watch changes to an object of kind PacketCapture. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedPacketCapture","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the PacketCapture","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagedkubernetesnetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedKubernetesNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagedkubernetesnetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind StagedKubernetesNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedKubernetesNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the StagedKubernetesNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagednetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/namespaces/{namespace}/stagednetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind StagedNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NamespacedStagedNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the StagedNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"object name and auth scope, such as for teams and projects","name":"namespace","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/networkpolicies":{"get":{"description":"watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NetworkPolicyListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/networksets":{"get":{"description":"watch individual changes to a list of NetworkSet. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3NetworkSetListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"NetworkSet"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/packetcaptures":{"get":{"description":"watch individual changes to a list of PacketCapture. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3PacketCaptureListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"PacketCapture"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/profiles":{"get":{"description":"watch individual changes to a list of Profile. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3ProfileList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/profiles/{name}":{"get":{"description":"watch changes to an object of kind Profile. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3Profile","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Profile"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the Profile","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/remoteclusterconfigurations":{"get":{"description":"watch individual changes to a list of RemoteClusterConfiguration. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3RemoteClusterConfigurationList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/remoteclusterconfigurations/{name}":{"get":{"description":"watch changes to an object of kind RemoteClusterConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3RemoteClusterConfiguration","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"RemoteClusterConfiguration"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the RemoteClusterConfiguration","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagedglobalnetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedGlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedGlobalNetworkPolicyList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagedglobalnetworkpolicies/{name}":{"get":{"description":"watch changes to an object of kind StagedGlobalNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedGlobalNetworkPolicy","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedGlobalNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the StagedGlobalNetworkPolicy","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagedkubernetesnetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedKubernetesNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedKubernetesNetworkPolicyListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedKubernetesNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/stagednetworkpolicies":{"get":{"description":"watch individual changes to a list of StagedNetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3StagedNetworkPolicyListForAllNamespaces","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"StagedNetworkPolicy"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/tiers":{"get":{"description":"watch individual changes to a list of Tier. deprecated: use the 'watch' parameter with a list operation instead.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3TierList","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watchlist","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/apis/projectcalico.org/v3/watch/tiers/{name}":{"get":{"description":"watch changes to an object of kind Tier. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.","consumes":["*/*"],"produces":["application/json","application/yaml","application/json;stream=watch"],"schemes":["https"],"tags":["projectcalicoOrg_v3"],"operationId":"watchProjectcalicoOrgV3Tier","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"}}},"x-kubernetes-action":"watch","x-kubernetes-group-version-kind":{"group":"projectcalico.org","version":"v3","kind":"Tier"}},"parameters":[{"uniqueItems":true,"type":"boolean","description":"allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.","name":"allowWatchBookmarks","in":"query"},{"uniqueItems":true,"type":"string","description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.","name":"continue","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.","name":"fieldSelector","in":"query"},{"uniqueItems":true,"type":"string","description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.","name":"labelSelector","in":"query"},{"uniqueItems":true,"type":"integer","description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.","name":"limit","in":"query"},{"uniqueItems":true,"type":"string","description":"name of the Tier","name":"name","in":"path","required":true},{"uniqueItems":true,"type":"string","description":"If 'true', then the output is pretty printed.","name":"pretty","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersion","in":"query"},{"uniqueItems":true,"type":"string","description":"resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset","name":"resourceVersionMatch","in":"query"},{"uniqueItems":true,"type":"integer","description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.","name":"timeoutSeconds","in":"query"},{"uniqueItems":true,"type":"boolean","description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.","name":"watch","in":"query"}]},"/version/":{"get":{"description":"get the code version","consumes":["application/json"],"produces":["application/json"],"schemes":["https"],"tags":["version"],"operationId":"getCodeVersion","responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.version.Info"}}}}}},"definitions":{"com.github.projectcalico.libcalico-go.lib.apis.v1.IPIPConfiguration":{"type":"object","properties":{"enabled":{"description":"When enabled is true, ipip tunneling will be used to deliver packets to destinations within this pool.","type":"boolean"},"mode":{"description":"The IPIP mode. This can be one of \"always\" or \"cross-subnet\". A mode of \"always\" will also use IPIP tunneling for routing to destination IP addresses within this pool. A mode of \"cross-subnet\" will only use IPIP tunneling when the destination node is on a different subnet to the originating node. The default value (if not specified) is \"always\".","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuditEventsSelection":{"description":"AuditEventsSelection defines which set of resources should be audited.","type":"object","properties":{"resources":{"description":"Resources lists the resources that will be included in the audit logs in the ReportData. Blank fields in the listed ResourceID structs are treated as wildcards.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuditResource"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuditResource":{"description":"AuditResource is used to filter Audit events in the Report configuration.\n\nAn empty field value indicates a wildcard. For example, if Resource is set to \"networkpolicies\" and all other fields are blank then this filter would include all NetworkPolicy resources across all namespaces, and would include both Calico and Kubernetes resource types.","type":"object","properties":{"apiGroup":{"description":"APIGroup is the name of the API group that contains the referred object (e.g. projectcalico.org).","type":"string"},"apiVersion":{"description":"APIVersion is the version of the API group that contains the referred object (e.g. v3).","type":"string"},"name":{"description":"The resource name.","type":"string"},"namespace":{"description":"The resource namespace.","type":"string"},"resource":{"description":"The resource type. The format is the lowercase plural as used in audit event selection and RBAC configuration.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthenticationReviewStatus":{"type":"object","properties":{"extra":{"type":"object","additionalProperties":{"type":"array","items":{"type":"string"}}},"groups":{"type":"array","items":{"type":"string"}},"name":{"type":"string"},"uid":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewResourceAttributes":{"type":"object","properties":{"apiGroup":{"description":"The API Group to check.","type":"string"},"resources":{"description":"The set of resources to check within the same API Group.","type":"array","items":{"type":"string"}},"verbs":{"description":"The set of verbs to check. This is expanded for each resource and within the same API Group.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewSpec":{"type":"object","properties":{"resourceAttributes":{"description":"The set of resource attributes that are being checked. Each resource attribute is expanded into individual kind/resource and verbs.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewResourceAttributes"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewStatus":{"type":"object","properties":{"authorizedResourceVerbs":{"description":"The set of authorized resource actions. A given API Group and resource combination will appear at most once in this slice.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerbs"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceGroup":{"type":"object","required":["namespace"],"properties":{"namespace":{"description":"The namespace. If this is empty then the user is authorized cluster-wide (i.e. across all namespaces). This will always be empty for cluster-scoped resources when the user is authorized.","type":"string"},"tier":{"description":"The tier. This is only valid for tiered policies, and tiers.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerb":{"type":"object","required":["verb","resourceGroups"],"properties":{"resourceGroups":{"description":"The group of resource instances that are authorized for this verb.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceGroup"}},"verb":{"description":"The verb.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerbs":{"type":"object","properties":{"apiGroup":{"description":"The API group.","type":"string"},"resource":{"description":"The resource.","type":"string"},"verbs":{"description":"The set of authorized actions for this resource. For a specific verb, this contains the set of resources for which the user is authorized to perform that action. This is calculated to avoid duplication such that a single resource instance can only be associated with a single entry in this slice. This allows a consumer of this API to issue a minimal set of queries (e.g. watches) that cover, uniquely, the authorized set of resources.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizedResourceVerb"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.AutoHostEndpointConfig":{"type":"object","properties":{"autoCreate":{"description":"AutoCreate enables automatic creation of host endpoints for every node. [Default: Disabled]","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.BGPConfigurationSpec":{"description":"BGPConfigurationSpec contains the values of the BGP configuration.","type":"object","properties":{"asNumber":{"description":"ASNumber is the default AS number used by a node. [Default: 64512]","type":"integer","format":"int64"},"communities":{"description":"Communities is a list of BGP community values and their arbitrary names for tagging routes.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Community"}},"extensions":{"description":"Extensions is a mapping of keys to values that can be used in custom BGP templates","type":"object","additionalProperties":{"type":"string"}},"listenPort":{"description":"ListenPort is the port where BGP protocol should listen. Defaults to 179","type":"integer","format":"int32"},"logSeverityScreen":{"description":"LogSeverityScreen is the log severity above which logs are sent to the stdout. [Default: INFO]","type":"string"},"nodeToNodeMeshEnabled":{"description":"NodeToNodeMeshEnabled sets whether full node to node BGP mesh is enabled. [Default: true]","type":"boolean"},"prefixAdvertisements":{"description":"PrefixAdvertisements contains per-prefix advertisement configuration.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.PrefixAdvertisement"}},"serviceClusterIPs":{"description":"ServiceClusterIPs are the CIDR blocks from which service cluster IPs are allocated. If specified, Calico will advertise these blocks, as well as any cluster IPs within them.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceClusterIPBlock"}},"serviceExternalIPs":{"description":"ServiceExternalIPs are the CIDR blocks for Kubernetes Service External IPs. Kubernetes Service ExternalIPs will only be advertised if they are within one of these blocks.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceExternalIPBlock"}},"serviceLoadBalancerIPs":{"description":"ServiceLoadBalancerIPs are the CIDR blocks for Kubernetes Service LoadBalancer IPs. Kubernetes Service status.LoadBalancer.Ingress IPs will only be advertised if they are within one of these blocks.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceLoadBalancerIPBlock"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPassword":{"description":"BGPPassword contains ways to specify a BGP password.","type":"object","properties":{"secretKeyRef":{"description":"Selects a key of a secret in the node pod's namespace.","$ref":"#/definitions/io.k8s.api.core.v1.SecretKeySelector"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPeerSpec":{"description":"BGPPeerSpec contains the specification for a BGPPeer resource.","type":"object","properties":{"asNumber":{"description":"The AS Number of the peer.","type":"integer","format":"int64"},"birdGatewayMode":{"description":"Specifies the BIRD \"gateway\" mode, i.e. method for computing the immediate next hop for each received route, for peerings generated by this BGPPeer resource. Default value \"Recursive\" means \"gateway recursive\". \"DirectIfDirectlyConnected\" means to configure \"gateway direct\" when the peer is directly connected.","type":"string"},"extensions":{"description":"Extensions is a mapping of keys to values that can be used in custom BGP templates","type":"object","additionalProperties":{"type":"string"}},"failureDetectionMode":{"description":"Specifies whether and how to detect loss of connectivity on the peerings generated by this BGPPeer resource. Default value \"None\" means nothing beyond BGP's own (slow) hold timer. \"BFDIfDirectlyConnected\" means to use BFD when the peer is directly connected.","type":"string"},"keepOriginalNextHop":{"description":"Option to keep the original nexthop field when routes are sent to a BGP Peer. Setting \"true\" configures the selected BGP Peers node to use the \"next hop keep;\" instead of \"next hop self;\"(default) in the specific branch of the Node on \"bird.cfg\".","type":"boolean"},"maxRestartTime":{"description":"Time to allow for software restart. When specified, this is configured as the graceful restart timeout when RestartMode is \"GracefulRestart\", and as the LLGR stale time when RestartMode is \"LongLivedGracefulRestart\". When not specified, the BIRD defaults are used, which are 120s for \"GracefulRestart\" and 3600s for \"LongLivedGracefulRestart\".","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"node":{"description":"The node name identifying the Calico node instance that is targeted by this peer. If this is not set, and no nodeSelector is specified, then this BGP peer selects all nodes in the cluster.","type":"string"},"nodeSelector":{"description":"Selector for the nodes that should have this peering. When this is set, the Node field must be empty.","type":"string"},"password":{"description":"Optional BGP password for the peerings generated by this BGPPeer resource.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPassword"},"peerIP":{"description":"The IP address of the peer followed by an optional port number to peer with. If port number is given, format should be `[\u003cIPv6\u003e]:port` or `\u003cIPv4\u003e:\u003cport\u003e` for IPv4. If optional port number is not set, and this peer IP and ASNumber belongs to a calico/node with ListenPort set in BGPConfiguration, then we use that port to peer.","type":"string"},"peerSelector":{"description":"Selector for the remote nodes to peer with. When this is set, the PeerIP and ASNumber fields must be empty. For each peering between the local node and selected remote nodes, we configure an IPv4 peering if both ends have NodeBGPSpec.IPv4Address specified, and an IPv6 peering if both ends have NodeBGPSpec.IPv6Address specified. The remote AS number comes from the remote node's NodeBGPSpec.ASNumber, or the global default if that is not set.","type":"string"},"restartMode":{"description":"Specifies restart behaviour to configure on the peerings generated by this BGPPeer resource. Default value \"GracefulRestart\" means traditional graceful restart. \"LongLivedGracefulRestart\" means LLGR according to draft-uttaro-idr-bgp-persistence-05.","type":"string"},"sourceAddress":{"description":"Specifies whether and how to configure a source address for the peerings generated by this BGPPeer resource. Default value \"UseNodeIP\" means to configure the node IP as the source address. \"None\" means not to configure a source address.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkFilter":{"description":"CISBenchmarkFilter provides filters for a set of benchmarks that match particular selection criteria.","type":"object","properties":{"benchmarkSelection":{"description":"BenchmarkSelection specifies which benchmarks this filter applies to. If not specified, applies to all.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkSelection"},"exclude":{"description":"Exclude is an array of test indices to exclude from the report.","type":"array","items":{"type":"string"}},"include":{"description":"Include is an array of test indices to show in the report. Is additive if IncludeUnscoredTests is true. Takes precedence over Exclude.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkParams":{"description":"CISBenchmarkParams contains the parameters for configuring a CIS benchmark report.","type":"object","properties":{"highThreshold":{"description":"Interpretted as a percentage to indicate at what levels of passing tests a node should be considered HIGH, MED, and LOW. - If \u003e= HighThreshold flag as high - Otherwise, if \u003e MedThreshold flag as med - Otherwise flag as low.","type":"integer","format":"int32"},"includeUnscoredTests":{"description":"Specifies if the report should also show results for scored/not-scored tests.","type":"boolean"},"medThreshold":{"type":"integer","format":"int32"},"numFailedTests":{"description":"Configure the number of top failed tests to show up on the report.","type":"integer","format":"int32"},"resultsFilters":{"description":"Benchmark results filters. The first matching set of filters is applied to each set of benchmark results. If there are no matching filters, the full set of benchmark results will be included in the report.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkFilter"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkSelection":{"description":"CISBenchmarkSelection selects a particular set of benchmarks.","type":"object","properties":{"kubernetesVersion":{"description":"KubernetesVersion is used select nodes that are running a specific version of kubelet. The full version need not be fully specified down to the patch level, in which case the significant parts of the version are matched. e.g. \"1.0\" will match versions \"1.0.1\" and \"1.0.2\" If not specified, matches all versions.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ClusterInformationSpec":{"description":"ClusterInformationSpec contains the values of describing the cluster.","type":"object","properties":{"calicoVersion":{"description":"CalicoVersion is the version of Calico that the cluster is running","type":"string"},"clusterGUID":{"description":"ClusterGUID is the GUID of the cluster","type":"string"},"clusterType":{"description":"ClusterType describes the type of the cluster","type":"string"},"cnxVersion":{"description":"CNXVersion is the version of CNX that the cluster is running","type":"string"},"datastoreReady":{"description":"DatastoreReady is used during significant datastore migrations to signal to components such as Felix that it should wait before accessing the datastore.","type":"boolean"},"variant":{"description":"Variant declares which variant of Calico should be active.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.Community":{"description":"Community contains standard or large community value and its name.","type":"object","properties":{"name":{"description":"Name given to community value.","type":"string"},"value":{"description":"Value must be of format `aa:nn` or `aa:nn:mm`. For standard community use `aa:nn` format, where `aa` and `nn` are 16 bit number. For large community use `aa:nn:mm` format, where `aa`, `nn` and `mm` are 32 bit number. Where, `aa` is an AS Number, `nn` and `mm` are per-AS identifier.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.CompletedReportJob":{"description":"CompletedReportJob augments the ReportJob with completion details.","type":"object","required":["start","end","job"],"properties":{"end":{"description":"The end time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"job":{"description":"A reference to the report creation job if known.","$ref":"#/definitions/io.k8s.api.core.v1.ObjectReference"},"jobCompletionTime":{"description":"The time the report job completed.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"start":{"description":"The start time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ControllersConfig":{"description":"ControllersConfig enables and configures individual Kubernetes controllers","type":"object","properties":{"federatedServices":{"description":"FederatedServices enables and configures the federatedservices controller. Disabled by default.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.FederatedServicesControllerConfig"},"namespace":{"description":"Namespace enables and configures the namespace controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NamespaceControllerConfig"},"node":{"description":"Node enables and configures the node controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NodeControllerConfig"},"policy":{"description":"Policy enables and configures the policy controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.PolicyControllerConfig"},"serviceAccount":{"description":"ServiceAccount enables and configures the service account controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountControllerConfig"},"workloadEndpoint":{"description":"WorkloadEndpoint enables and configures the workload endpoint controller. Enabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.WorkloadEndpointControllerConfig"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EgressSpec":{"type":"object","properties":{"namespaceSelector":{"description":"NamespaceSelector","type":"string"},"selector":{"description":"Selector","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointPort":{"type":"object","required":["name","protocol","port"],"properties":{"name":{"type":"string"},"port":{"type":"integer","format":"int32"},"protocol":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Protocol"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointsSelection":{"description":"EndpointsSelection is a set of selectors used to select the endpoints that are considered to be in-scope for the report. An empty selector is equivalent to all(). All three selectors are ANDed together.","type":"object","properties":{"namespaces":{"description":"Namespace match restricts endpoint selection to those in the selected namespaces.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NamesAndLabelsMatch"},"selector":{"description":"Selector, selects endpoints by endpoint labels. If omitted, all endpoints are included in the report data.","type":"string"},"serviceAccounts":{"description":"ServiceAccount match restricts endpoint selection to those in the selected service accounts.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NamesAndLabelsMatch"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.EntityRule":{"description":"An EntityRule is a sub-component of a Rule comprising the match criteria specific to a particular entity (that is either the source or destination).\n\nA source EntityRule matches the source endpoint and originating traffic. A destination EntityRule matches the destination endpoint and terminating traffic.","type":"object","properties":{"domains":{"description":"Domains is an optional field, valid for egress Allow rules only, that restricts the rule to apply only to traffic to one of the specified domains. If this field is specified, Action must be Allow, and Nets and Selector must both be left empty.","type":"array","items":{"type":"string"}},"namespaceSelector":{"description":"NamespaceSelector is an optional field that contains a selector expression. Only traffic that originates from (or terminates at) endpoints within the selected namespaces will be matched. When both NamespaceSelector and Selector are defined on the same rule, then only workload endpoints that are matched by both selectors will be selected by the rule.\n\nFor NetworkPolicy, an empty NamespaceSelector implies that the Selector is limited to selecting only workload endpoints in the same namespace as the NetworkPolicy.\n\nFor NetworkPolicy, `global()` NamespaceSelector implies that the Selector is limited to selecting only GlobalNetworkSet or HostEndpoint.\n\nFor GlobalNetworkPolicy, an empty NamespaceSelector implies the Selector applies to workload endpoints across all namespaces.","type":"string"},"nets":{"description":"Nets is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) IP addresses in any of the given subnets.","type":"array","items":{"type":"string"}},"notNets":{"description":"NotNets is the negated version of the Nets field.","type":"array","items":{"type":"string"}},"notPorts":{"description":"NotPorts is the negated version of the Ports field. Since only some protocols have ports, if any ports are specified it requires the Protocol match in the Rule to be set to \"TCP\" or \"UDP\".","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"}},"notSelector":{"description":"NotSelector is the negated version of the Selector field. See Selector field for subtleties with negated selectors.","type":"string"},"ports":{"description":"Ports is an optional field that restricts the rule to only apply to traffic that has a source (destination) port that matches one of these ranges/values. This value is a list of integers or strings that represent ranges of ports.\n\nSince only some protocols have ports, if any ports are specified it requires the Protocol match in the Rule to be set to \"TCP\" or \"UDP\".","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"}},"selector":{"description":"Selector is an optional field that contains a selector expression (see Policy for sample syntax). Only traffic that originates from (terminates at) endpoints matching the selector will be matched.\n\nNote that: in addition to the negated version of the Selector (see NotSelector below), the selector expression syntax itself supports negation. The two types of negation are subtly different. One negates the set of matched endpoints, the other negates the whole match:\n\n\tSelector = \"!has(my_label)\" matches packets that are from other Calico-controlled\n\tendpoints that do not have the label \"my_label\".\n\n\tNotSelector = \"has(my_label)\" matches packets that are not from Calico-controlled\n\tendpoints that do have the label \"my_label\".\n\nThe effect is that the latter will accept packets from non-Calico sources whereas the former is limited to packets from Calico-controlled endpoints.","type":"string"},"serviceAccounts":{"description":"ServiceAccounts is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) a pod running as a matching service account.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountMatch"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ErrorCondition":{"type":"object","required":["type","message"],"properties":{"message":{"type":"string"},"type":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.FederatedServicesControllerConfig":{"description":"FederatedServicesControllerConfig configures the federated services controller, which syncs Kubernetes services from remote clusters.","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.FelixConfigurationSpec":{"description":"FelixConfigurationSpec contains the values of the Felix configuration.","type":"object","properties":{"allowIPIPPacketsFromWorkloads":{"description":"AllowIPIPPacketsFromWorkloads controls whether Felix will add a rule to drop IPIP encapsulated traffic from workloads [Default: false]","type":"boolean"},"allowVXLANPacketsFromWorkloads":{"description":"AllowVXLANPacketsFromWorkloads controls whether Felix will add a rule to drop VXLAN encapsulated traffic from workloads [Default: false]","type":"boolean"},"awsSrcDstCheck":{"description":"Set source-destination-check on AWS EC2 instances. Accepted value must be one of \"DoNothing\", \"Enabled\" or \"Disabled\". [Default: DoNothing]","type":"string"},"bpfConnectTimeLoadBalancingEnabled":{"description":"BPFConnectTimeLoadBalancingEnabled when in BPF mode, controls whether Felix installs the connection-time load balancer. The connect-time load balancer is required for the host to be able to reach Kubernetes services and it improves the performance of pod-to-service connections. The only reason to disable it is for debugging purposes. [Default: true]","type":"boolean"},"bpfDataIfacePattern":{"description":"BPFDataIfacePattern is a regular expression that controls which interfaces Felix should attach BPF programs to in order to catch traffic to/from the network. This needs to match the interfaces that Calico workload traffic flows over as well as any interfaces that handle incoming traffic to nodeports and services from outside the cluster. It should not match the workload interfaces (usually named cali...).","type":"string"},"bpfDisableUnprivileged":{"description":"BPFDisableUnprivileged, if enabled, Felix sets the kernel.unprivileged_bpf_disabled sysctl to disable unprivileged use of BPF. This ensures that unprivileged users cannot access Calico's BPF maps and cannot insert their own BPF programs to interfere with Calico's. [Default: true]","type":"boolean"},"bpfEnabled":{"description":"BPFEnabled, if enabled Felix will use the BPF dataplane. [Default: false]","type":"boolean"},"bpfExternalServiceMode":{"description":"BPFExternalServiceMode in BPF mode, controls how connections from outside the cluster to services (node ports and cluster IPs) are forwarded to remote workloads. If set to \"Tunnel\" then both request and response traffic is tunneled to the remote node. If set to \"DSR\", the request traffic is tunneled but the response traffic is sent directly from the remote node. In \"DSR\" mode, the remote node appears to use the IP of the ingress node; this requires a permissive L2 network. [Default: Tunnel]","type":"string"},"bpfKubeProxyEndpointSlicesEnabled":{"description":"BPFKubeProxyEndpointSlicesEnabled in BPF mode, controls whether Felix's embedded kube-proxy accepts EndpointSlices or not.","type":"boolean"},"bpfKubeProxyIptablesCleanupEnabled":{"description":"BPFKubeProxyIptablesCleanupEnabled, if enabled in BPF mode, Felix will proactively clean up the upstream Kubernetes kube-proxy's iptables chains. Should only be enabled if kube-proxy is not running. [Default: true]","type":"boolean"},"bpfKubeProxyMinSyncPeriod":{"description":"BPFKubeProxyMinSyncPeriod, in BPF mode, controls the minimum time between updates to the dataplane for Felix's embedded kube-proxy. Lower values give reduced set-up latency. Higher values reduce Felix CPU usage by batching up more work. [Default: 1s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"bpfLogLevel":{"description":"BPFLogLevel controls the log level of the BPF programs when in BPF dataplane mode. One of \"Off\", \"Info\", or \"Debug\". The logs are emitted to the BPF trace pipe, accessible with the command `tc exec bpf debug`. [Default: Off].","type":"string"},"captureDir":{"description":"CaptureDir controls directory to store file capture. [Default: /var/log/calico/pcap]","type":"string"},"captureMaxFiles":{"description":"CaptureMaxFiles controls number of rotated capture file to keep. [Default: 2]","type":"integer","format":"int32"},"captureMaxSizeBytes":{"description":"CaptureMaxSizeBytes controls the max size of a file capture. [Default: 10000000]","type":"integer","format":"int32"},"captureRotationSeconds":{"description":"CaptureRotationSeconds controls the time rotation of a packet capture. [Default: 3600]","type":"integer","format":"int32"},"chainInsertMode":{"description":"ChainInsertMode controls whether Felix hooks the kernel's top-level iptables chains by inserting a rule at the top of the chain or by appending a rule at the bottom. insert is the safe default since it prevents Calico's rules from being bypassed. If you switch to append mode, be sure that the other rules in the chains signal acceptance by falling through to the Calico rules, otherwise the Calico policy will be bypassed. [Default: insert]","type":"string"},"cloudWatchLogsAggregationKindForAllowed":{"description":"CloudWatchLogsAggregationKindForAllowed is used to choose the type of aggregation for flow log entries created for allowed connections. [Default: 2 - pod prefix name based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggreagation.","type":"integer","format":"int32"},"cloudWatchLogsAggregationKindForDenied":{"description":"CloudWatchLogsAggregationKindForDenied is used to choose the type of aggregation for flow log entries created for denied connections. [Default: 1 - source port based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggreagation.","type":"integer","format":"int32"},"cloudWatchLogsEnableHostEndpoint":{"description":"Deprecated: Use FlowLogsEnableHostEndpoint.","type":"boolean"},"cloudWatchLogsEnabledForAllowed":{"description":"CloudWatchLogsEnabledForAllowed is used to enable/disable flow logs entries created for allowed connections. Default is true. This parameter only takes effect when CloudWatchLogsReporterEnabled is set to true.","type":"boolean"},"cloudWatchLogsEnabledForDenied":{"description":"CloudWatchLogsEnabledForDenied is used to enable/disable flow logs entries created for denied flows. Default is true. This parameter only takes effect when CloudWatchLogsReporterEnabled is set to true.","type":"boolean"},"cloudWatchLogsFlushInterval":{"description":"Deprecated: Use FlowLogsFlushInterval instead.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"cloudWatchLogsIncludeLabels":{"description":"CloudWatchLogsIncludeLabels is used to configure if endpoint labels are included in a Flow log entry.","type":"boolean"},"cloudWatchLogsIncludePolicies":{"description":"CloudWatchLogsIncludePolicies is used to configure if policy information are included in a Flow log entry.","type":"boolean"},"cloudWatchLogsLogGroupName":{"description":"CloudWatchLogsLogGroupName configures the Log group to use for exporting flow logs. Defaults to \"tigera-flowlogs-\u003ccluster-guid\u003e\".","type":"string"},"cloudWatchLogsLogStreamName":{"description":"CloudWatchLogsLogStreamName configures the Log stream to use for exporting flow logs. Defaults to \"\u003cfelix-hostname\u003e_Flowlogs\".","type":"string"},"cloudWatchLogsReporterEnabled":{"description":"Enable Flow logs reporting to AWS CloudWatch.","type":"boolean"},"cloudWatchLogsRetentionDays":{"description":"Number of days for which to retain logs. See https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutRetentionPolicy.html for allowed values.","type":"integer","format":"int32"},"cloudWatchMetricsPushIntervalSecs":{"description":"CloudWatchMetricsPushInterval configures the interval at which Felix exports metrics to CloudWatch.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"cloudWatchMetricsReporterEnabled":{"description":"Enable reporting metrics to CloudWatch.","type":"boolean"},"cloudWatchNodeHealthPushIntervalSecs":{"description":"CloudWatchNodeHealthPushIntervalSecs configures the frequency of pushing the node health metrics to CloudWatch.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"cloudWatchNodeHealthStatusEnabled":{"description":"CloudWatchNodeHealthStatusEnabled enables pushing node health data to CloudWatch.","type":"boolean"},"dataplaneDriver":{"type":"string"},"debugDisableLogDropping":{"type":"boolean"},"debugMemoryProfilePath":{"type":"string"},"debugSimulateCalcGraphHangAfter":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"debugSimulateDataplaneHangAfter":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"defaultEndpointToHostAction":{"description":"DefaultEndpointToHostAction controls what happens to traffic that goes from a workload endpoint to the host itself (after the traffic hits the endpoint egress policy). By default Calico blocks traffic from workload endpoints to the host itself with an iptables \"DROP\" action. If you want to allow some or all traffic from endpoint to host, set this parameter to RETURN or ACCEPT. Use RETURN if you have your own rules in the iptables \"INPUT\" chain; Calico will insert its rules at the top of that chain, then \"RETURN\" packets to the \"INPUT\" chain once it has completed processing workload endpoint egress policy. Use ACCEPT to unconditionally accept packets from workloads after processing workload endpoint egress policy. [Default: Drop]","type":"string"},"deletedMetricsRetentionSecs":{"type":"integer","format":"int32"},"deviceRouteProtocol":{"description":"This defines the route protocol added to programmed device routes, by default this will be RTPROT_BOOT when left blank.","type":"integer","format":"int32"},"deviceRouteSourceAddress":{"description":"This is the source address to use on programmed device routes. By default the source address is left blank, leaving the kernel to choose the source address used.","type":"string"},"disableConntrackInvalidCheck":{"type":"boolean"},"dnsCacheEpoch":{"description":"An arbitrary number that can be changed, at runtime, to tell Felix to discard all its learnt DNS information. [Default: 0].","type":"integer","format":"int32"},"dnsCacheFile":{"description":"The name of the file that Felix uses to preserve learnt DNS information when restarting. [Default: \"/var/run/calico/felix-dns-cache.txt\"].","type":"string"},"dnsCacheSaveInterval":{"description":"The periodic interval at which Felix saves learnt DNS information to the cache file. [Default: 60s].","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"dnsExtraTTL":{"description":"Extra time to keep IPs and alias names that are learnt from DNS, in addition to each name or IP's advertised TTL. [Default: 0s].","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"dnsLogsFileAggregationKind":{"description":"DNSLogsFileAggregationKind is used to choose the type of aggregation for DNS log entries. [Default: 1 - client name prefix aggregation]. Accepted values are 0 and 1. 0 - No aggregation 1 - Aggregate over clients with the same name prefix","type":"integer","format":"int32"},"dnsLogsFileDirectory":{"description":"DNSLogsFileDirectory sets the directory where DNS log files are stored. [Default: /var/log/calico/dnslogs]","type":"string"},"dnsLogsFileEnabled":{"description":"DNSLogsFileEnabled controls logging DNS logs to a file. If false no DNS logging to file will occur. [Default: false]","type":"boolean"},"dnsLogsFileIncludeLabels":{"description":"DNSLogsFileIncludeLabels is used to configure if endpoint labels are included in a DNS log entry written to file. [Default: true]","type":"boolean"},"dnsLogsFileMaxFileSizeMB":{"description":"DNSLogsFileMaxFileSizeMB sets the max size in MB of DNS log files before rotation. [Default: 100]","type":"integer","format":"int32"},"dnsLogsFileMaxFiles":{"description":"DNSLogsFileMaxFiles sets the number of DNS log files to keep. [Default: 5]","type":"integer","format":"int32"},"dnsLogsFilePerNodeLimit":{"description":"Limit on the number of DNS logs that can be emitted within each flush interval. When this limit has been reached, Felix counts the number of unloggable DNS responses within the flush interval, and emits a WARNING log with that count at the same time as it flushes the buffered DNS logs. [Default: 0, meaning no limit]","type":"integer","format":"int32"},"dnsLogsFlushInterval":{"description":"DNSLogsFlushInterval configures the interval at which Felix exports DNS logs. [Default: 300s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"dnsLogsLatency":{"description":"DNSLogsLatency indicates to include measurements of DNS request/response latency in each DNS log. [Default: true]","type":"boolean"},"dnsTrustedServers":{"description":"The DNS servers that Felix should trust. Each entry here must be `\u003cip\u003e[:\u003cport\u003e]` - indicating an explicit DNS server IP - or `k8s-service:[\u003cnamespace\u003e/]\u003cname\u003e[:port]` - indicating a Kubernetes DNS service. `\u003cport\u003e` defaults to the first service port, or 53 for an IP, and `\u003cnamespace\u003e` to `kube-system`. An IPv6 address with a port must use the square brackets convention, for example `[fd00:83a6::12]:5353`.Note that Felix (calico-node) will need RBAC permission to read the details of each service specified by a `k8s-service:...` form. [Default: \"k8s-service:kube-dns\"].","type":"array","items":{"type":"string"}},"dropActionOverride":{"description":"DropActionOverride overrides the Drop action in Felix, optionally changing the behavior to Accept, and optionally adding Log. Possible values are Drop, LogAndDrop, Accept, LogAndAccept. [Default: Drop]","type":"string"},"egressIPRoutingRulePriority":{"description":"EgressIPRoutingRulePriority controls the priority value to use for the egress IP routing rule. [Default: 100]","type":"integer","format":"int32"},"egressIPSupport":{"description":"EgressIPSupport defines three different support modes for egress IP function. [Default: Disabled] - Disabled: Egress IP function is disabled. - EnabledPerNamespace: Egress IP function is enabled and can be configured on a per-namespace basis;\n per-pod egress annotations are ignored.\n- EnabledPerNamespaceOrPerPod: Egress IP function is enabled and can be configured per-namespace or per-pod,\n with per-pod egress annotations overriding namespace annotations.","type":"string"},"egressIPVXLANPort":{"description":"EgressIPVXLANPort is the port number of vxlan tunnel device for egress traffic. [Default: 4790]","type":"integer","format":"int32"},"egressIPVXLANVNI":{"description":"EgressIPVXLANVNI is the VNI ID of vxlan tunnel device for egress traffic. [Default: 4097]","type":"integer","format":"int32"},"endpointReportingDelay":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"endpointReportingEnabled":{"type":"boolean"},"externalNodesList":{"description":"ExternalNodesCIDRList is a list of CIDR's of external-non-calico-nodes which may source tunnel traffic and have the tunneled traffic be accepted at calico nodes.","type":"array","items":{"type":"string"}},"failsafeInboundHostPorts":{"description":"FailsafeInboundHostPorts is a comma-delimited list of UDP/TCP ports that Felix will allow incoming traffic to host endpoints on irrespective of the security policy. This is useful to avoid accidentally cutting off a host with incorrect configuration. Each port should be specified as tcp:\u003cport-number\u003e or udp:\u003cport-number\u003e. For back-compatibility, if the protocol is not specified, it defaults to \"tcp\". To disable all inbound host ports, use the value none. The default value allows ssh access and DHCP. [Default: tcp:22, udp:68, tcp:179, tcp:2379, tcp:2380, tcp:6443, tcp:6666, tcp:6667]","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ProtoPort"}},"failsafeOutboundHostPorts":{"description":"FailsafeOutboundHostPorts is a comma-delimited list of UDP/TCP ports that Felix will allow outgoing traffic from host endpoints to irrespective of the security policy. This is useful to avoid accidentally cutting off a host with incorrect configuration. Each port should be specified as tcp:\u003cport-number\u003e or udp:\u003cport-number\u003e. For back-compatibility, if the protocol is not specified, it defaults to \"tcp\". To disable all outbound host ports, use the value none. The default value opens etcd's standard ports to ensure that Felix does not get cut off from etcd as well as allowing DHCP and DNS. [Default: tcp:179, tcp:2379, tcp:2380, tcp:6443, tcp:6666, tcp:6667, udp:53, udp:67]","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ProtoPort"}},"featureDetectOverride":{"description":"FeatureDetectOverride is used to override the feature detection. Values are specified in a comma separated list with no spaces, example; \"SNATFullyRandom=true,MASQFullyRandom=false,RestoreSupportsLock=\". \"true\" or \"false\" will force the feature, empty or omitted values are auto-detected.","type":"string"},"flowLogsAggregationThresholdBytes":{"description":"FlowLogsAggregationThresholdBytes is used specify how far behind the external pipeline that reads flow logs can be. Default is 8192 bytes. This parameter only takes effect when FlowLogsDynamicAggregationEnabled is set to true.","type":"integer","format":"int32"},"flowLogsCollectProcessInfo":{"description":"FlowLogsCollectProcessInfo, if enabled Felix will load the kprobe BPF programs to collect process info. [Default: false]","type":"boolean"},"flowLogsCollectTcpStats":{"description":"FlowLogsCollectTcpStats enables flow logs reporting TCP socket stats","type":"boolean"},"flowLogsDynamicAggregationEnabled":{"description":"FlowLogsDynamicAggregationEnabled is used to enable/disable dynamically changing aggregation levels. Default is true.","type":"boolean"},"flowLogsEnableHostEndpoint":{"description":"FlowLogsEnableHostEndpoint enables Flow logs reporting for HostEndpoints.","type":"boolean"},"flowLogsEnableNetworkSets":{"description":"FlowLogsEnableNetworkSets enables Flow logs reporting for GlobalNetworkSets.","type":"boolean"},"flowLogsFileAggregationKindForAllowed":{"description":"FlowLogsFileAggregationKindForAllowed is used to choose the type of aggregation for flow log entries created for allowed connections. [Default: 2 - pod prefix name based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggreagation.","type":"integer","format":"int32"},"flowLogsFileAggregationKindForDenied":{"description":"FlowLogsFileAggregationKindForDenied is used to choose the type of aggregation for flow log entries created for denied connections. [Default: 1 - source port based aggregation]. Accepted values are 0, 1 and 2. 0 - No aggregation 1 - Source port based aggregation 2 - Pod prefix name based aggregation. 3 - No destination ports based aggregation","type":"integer","format":"int32"},"flowLogsFileDirectory":{"description":"FlowLogsFileDirectory sets the directory where flow logs files are stored.","type":"string"},"flowLogsFileEnabled":{"description":"FlowLogsFileEnabled when set to true, enables logging flow logs to a file. If false no flow logging to file will occur.","type":"boolean"},"flowLogsFileEnabledForAllowed":{"description":"FlowLogsFileEnabledForAllowed is used to enable/disable flow logs entries created for allowed connections. Default is true. This parameter only takes effect when FlowLogsFileReporterEnabled is set to true.","type":"boolean"},"flowLogsFileEnabledForDenied":{"description":"FlowLogsFileEnabledForDenied is used to enable/disable flow logs entries created for denied flows. Default is true. This parameter only takes effect when FlowLogsFileReporterEnabled is set to true.","type":"boolean"},"flowLogsFileIncludeLabels":{"description":"FlowLogsFileIncludeLabels is used to configure if endpoint labels are included in a Flow log entry written to file.","type":"boolean"},"flowLogsFileIncludePolicies":{"description":"FlowLogsFileIncludePolicies is used to configure if policy information are included in a Flow log entry written to file.","type":"boolean"},"flowLogsFileIncludeService":{"description":"FlowLogsFileIncludeService is used to configure if the destination service is included in a Flow log entry written to file. The service information can only be included if the flow was explicitly determined to be directed at the service (e.g. when the pre-DNAT destination corresponds to the service ClusterIP and port).","type":"boolean"},"flowLogsFileMaxFileSizeMB":{"description":"FlowLogsFileMaxFileSizeMB sets the max size in MB of flow logs files before rotation.","type":"integer","format":"int32"},"flowLogsFileMaxFiles":{"description":"FlowLogsFileMaxFiles sets the number of log files to keep.","type":"integer","format":"int32"},"flowLogsFilePerFlowProcessLimit":{"description":"FlowLogsFilePerFlowProcessLimit, is used to specify the maximum number of flow log entries with distinct process information beyond which process information will be aggregated. [Default: 2]","type":"integer","format":"int32"},"flowLogsFlushInterval":{"description":"FlowLogsFlushInterval configures the interval at which Felix exports flow logs.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"flowLogsMaxOriginalIPsIncluded":{"description":"FlowLogsMaxOriginalIPsIncluded specifies the number of unique IP addresses (if relevant) that should be included in Flow logs.","type":"integer","format":"int32"},"flowLogsPositionFilePath":{"description":"FlowLogsPositionFilePath is used specify the position of the external pipeline that reads flow logs. Default is /var/log/calico/flows.log.pos. This parameter only takes effect when FlowLogsDynamicAggregationEnabled is set to true.","type":"string"},"genericXDPEnabled":{"description":"GenericXDPEnabled enables Generic XDP so network cards that don't support XDP offload or driver modes can use XDP. This is not recommended since it doesn't provide better performance than iptables. [Default: false]","type":"boolean"},"healthEnabled":{"type":"boolean"},"healthHost":{"type":"string"},"healthPort":{"type":"integer","format":"int32"},"interfaceExclude":{"description":"InterfaceExclude is a comma-separated list of interfaces that Felix should exclude when monitoring for host endpoints. The default value ensures that Felix ignores Kubernetes' IPVS dummy interface, which is used internally by kube-proxy. If you want to exclude multiple interface names using a single value, the list supports regular expressions. For regular expressions you must wrap the value with '/'. For example having values '/^kube/,veth1' will exclude all interfaces that begin with 'kube' and also the interface 'veth1'. [Default: kube-ipvs0]","type":"string"},"interfacePrefix":{"description":"InterfacePrefix is the interface name prefix that identifies workload endpoints and so distinguishes them from host endpoint interfaces. Note: in environments other than bare metal, the orchestrators configure this appropriately. For example our Kubernetes and Docker integrations set the 'cali' value, and our OpenStack integration sets the 'tap' value. [Default: cali]","type":"string"},"interfaceRefreshInterval":{"description":"InterfaceRefreshInterval is the period at which Felix rescans local interfaces to verify their state. The rescan can be disabled by setting the interval to 0.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"ipipEnabled":{"type":"boolean"},"ipipMTU":{"description":"IPIPMTU is the MTU to set on the tunnel device. See Configuring MTU [Default: 1440]","type":"integer","format":"int32"},"ipsecAllowUnsecuredTraffic":{"description":"IPSecAllowUnsecuredTraffic controls whether non-IPsec traffic is allowed in addition to IPsec traffic. Enabling this negates the anti-spoofing protections of IPsec but it is useful when migrating to/from IPsec. [Default: false]","type":"boolean"},"ipsecESPAlgorithm":{"description":"IPSecESAlgorithm sets IPSec ESP algorithm. Default is NIST suite B recommendation. [Default: aes128gcm16-ecp256]","type":"string"},"ipsecIKEAlgorithm":{"description":"IPSecIKEAlgorithm sets IPSec IKE algorithm. Default is NIST suite B recommendation. [Default: aes128gcm16-prfsha256-ecp256]","type":"string"},"ipsecLogLevel":{"description":"IPSecLogLevel controls log level for IPSec components. Set to None for no logging. A generic log level terminology is used [None, Notice, Info, Debug, Verbose]. [Default: Info]","type":"string"},"ipsecMode":{"description":"IPSecMode controls which mode IPSec is operating on. Default value means IPSec is not enabled. [Default: \"\"]","type":"string"},"ipsecPolicyRefreshInterval":{"description":"IPSecPolicyRefreshInterval is the interval at which Felix will check the kernel's IPsec policy tables and repair any inconsistencies. [Default: 600s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"ipsetsRefreshInterval":{"description":"IpsetsRefreshInterval is the period at which Felix re-checks all iptables state to ensure that no other process has accidentally broken Calico's rules. Set to 0 to disable iptables refresh. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesBackend":{"description":"IptablesBackend specifies which backend of iptables will be used. The default is legacy.","type":"string"},"iptablesFilterAllowAction":{"type":"string"},"iptablesLockFilePath":{"description":"IptablesLockFilePath is the location of the iptables lock file. You may need to change this if the lock file is not in its standard location (for example if you have mapped it into Felix's container at a different path). [Default: /run/xtables.lock]","type":"string"},"iptablesLockProbeInterval":{"description":"IptablesLockProbeInterval is the time that Felix will wait between attempts to acquire the iptables lock if it is not available. Lower values make Felix more responsive when the lock is contended, but use more CPU. [Default: 50ms]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesLockTimeout":{"description":"IptablesLockTimeout is the time that Felix will wait for the iptables lock, or 0, to disable. To use this feature, Felix must share the iptables lock file with all other processes that also take the lock. When running Felix inside a container, this requires the /run directory of the host to be mounted into the calico/node or calico/felix container. [Default: 0s disabled]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesMangleAllowAction":{"type":"string"},"iptablesMarkMask":{"description":"IptablesMarkMask is the mask that Felix selects its IPTables Mark bits from. Should be a 32 bit hexadecimal number with at least 8 bits set, none of which clash with any other mark bits in use on the system. [Default: 0xff000000]","type":"integer","format":"int64"},"iptablesNATOutgoingInterfaceFilter":{"type":"string"},"iptablesPostWriteCheckInterval":{"description":"IptablesPostWriteCheckInterval is the period after Felix has done a write to the dataplane that it schedules an extra read back in order to check the write was not clobbered by another process. This should only occur if another application on the system doesn't respect the iptables lock. [Default: 1s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"iptablesRefreshInterval":{"description":"IptablesRefreshInterval is the period at which Felix re-checks the IP sets in the dataplane to ensure that no other process has accidentally broken Calico's rules. Set to 0 to disable IP sets refresh. Note: the default for this value is lower than the other refresh intervals as a workaround for a Linux kernel bug that was fixed in kernel version 4.11. If you are using v4.11 or greater you may want to set this to, a higher value to reduce Felix CPU usage. [Default: 10s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"ipv6Support":{"type":"boolean"},"kubeNodePortRanges":{"description":"KubeNodePortRanges holds list of port ranges used for service node ports. Only used if felix detects kube-proxy running in ipvs mode. Felix uses these ranges to separate host and workload traffic. [Default: 30000:32767].","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"}},"l7LogsFileAggregationDestinationInfo":{"description":"L7LogsFileAggregationDestinationInfo is used to choose the type of aggregation for the destination metadata on L7 log entries. [Default: IncludeL7DestinationInfo - include destination metadata]. Accepted values are IncludeL7DestinationInfo and ExcludeL7DestinationInfo. IncludeL7DestinationInfo - Include destination metadata in the logs. ExcludeL7DestinationInfo - Aggregate over all other fields ignoring the destination aggregated name, namespace, and type.","type":"string"},"l7LogsFileAggregationHTTPHeaderInfo":{"description":"L7LogsFileAggregationHTTPHeaderInfo is used to choose the type of aggregation for HTTP header data on L7 log entries. [Default: ExcludeL7HTTPHeaderInfo - http header info removal]. Accepted values are IncludeL7HTTPHeaderInfo and ExcludeL7HTTPHeaderInfo. IncludeL7HTTPHeaderInfo - Include HTTP header data in the logs. ExcludeL7HTTPHeaderInfo - Aggregate over all other fields ignoring the user agent and log type.","type":"string"},"l7LogsFileAggregationHTTPMethod":{"description":"L7LogsFileAggregationHTTPMethod is used to choose the type of aggregation for the HTTP request method on L7 log entries. [Default: IncludeL7HTTPMethod - include the HTTP method]. Accepted values are IncludeL7HTTPMethod and ExcludeL7HTTPMethod. IncludeL7HTTPMethod - Include HTTP method in the logs. ExcludeL7HTTPMethod - Aggregate over all other fields ignoring the HTTP method.","type":"string"},"l7LogsFileAggregationNumURLPath":{"description":"L7LogsFileAggregationNumURLPath is used to choose the number of components in the url path to display. This allows for the url to be truncated in case parts of the path provide no value. Setting this value to negative will allow all parts of the path to be displayed. [Default: 5].","type":"integer","format":"int32"},"l7LogsFileAggregationResponseCode":{"description":"L7LogsFileAggregationResponseCode is used to choose the type of aggregation for the response code on L7 log entries. [Default: IncludeL7ResponseCode - include the response code]. Accepted values are IncludeL7ResponseCode and ExcludeL7ResponseCode. IncludeL7ResponseCode - Include the response code in the logs. ExcludeL7ResponseCode - Aggregate over all other fields ignoring the response code.","type":"string"},"l7LogsFileAggregationServiceInfo":{"description":"L7LogsFileAggregationServiceInfo is used to choose the type of aggregation for the service data on L7 log entries. [Default: IncludeL7ServiceInfo - include service data]. Accepted values are IncludeL7ServiceInfo and ExcludeL7ServiceInfo. IncludeL7ServiceInfo - Include service data in the logs. ExcludeL7ServiceInfo - Aggregate over all other fields ignoring the service name, namespace, and port.","type":"string"},"l7LogsFileAggregationSourceInfo":{"description":"L7LogsFileAggregationExcludeSourceInfo is used to choose the type of aggregation for the source metadata on L7 log entries. [Default: IncludeL7SourceInfo - include source metadata]. Accepted values are IncludeL7SourceInfo and ExcludeL7SourceInfo. IncludeL7SourceInfo - Include source metadata in the logs. ExcludeL7SourceInfo - Aggregate over all other fields ignoring the source aggregated name, namespace, and type.","type":"string"},"l7LogsFileAggregationTrimURL":{"description":"L7LogsFileAggregationTrimURL is used to choose the type of aggregation for the url on L7 log entries. [Default: IncludeL7FullURL - include the full URL up to however many path components are allowed by L7LogsFileAggregationNumURLPath]. Accepted values are 0 and 1. IncludeL7FullURL - Include the full URL up to however many path components are allowed by L7LogsFileAggregationNumURLPath. TrimURLQuery - Aggregate over all other fields ignoring the query parameters on the URL. TrimURLQueryAndPath - Aggregate over all other fields and the base URL only. ExcludeL7URL - Aggregate over all other fields ignoring the URL entirely.","type":"string"},"l7LogsFileAggregationURLCharLimit":{"description":"Limit on the length of the URL collected in L7 logs. When a URL length reaches this limit it is sliced off, and the sliced URL is sent to log storage. [Default: 250]","type":"integer","format":"int32"},"l7LogsFileDirectory":{"description":"L7LogsFileDirectory sets the directory where L7 log files are stored. [Default: /var/log/calico/l7logs]","type":"string"},"l7LogsFileEnabled":{"description":"L7LogsFileEnabled controls logging L7 logs to a file. If false no L7 logging to file will occur. [Default: false]","type":"boolean"},"l7LogsFileMaxFileSizeMB":{"description":"L7LogsFileMaxFileSizeMB sets the max size in MB of L7 log files before rotation. [Default: 100]","type":"integer","format":"int32"},"l7LogsFileMaxFiles":{"description":"L7LogsFileMaxFiles sets the number of L7 log files to keep. [Default: 5]","type":"integer","format":"int32"},"l7LogsFilePerNodeLimit":{"description":"Limit on the number of L7 logs that can be emitted within each flush interval. When this limit has been reached, Felix counts the number of unloggable L7 responses within the flush interval, and emits a WARNING log with that count at the same time as it flushes the buffered L7 logs. [Default: 0, meaning no limit]","type":"integer","format":"int32"},"l7LogsFlushInterval":{"description":"L7LogsFlushInterval configures the interval at which Felix exports L7 logs. [Default: 300s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"logDropActionOverride":{"description":"LogDropActionOverride specifies whether or not to include the DropActionOverride in the logs when it is triggered.","type":"boolean"},"logFilePath":{"description":"LogFilePath is the full path to the Felix log. Set to none to disable file logging. [Default: /var/log/calico/felix.log]","type":"string"},"logPrefix":{"description":"LogPrefix is the log prefix that Felix uses when rendering LOG rules. [Default: calico-packet]","type":"string"},"logSeverityFile":{"description":"LogSeverityFile is the log severity above which logs are sent to the log file. [Default: Info]","type":"string"},"logSeverityScreen":{"description":"LogSeverityScreen is the log severity above which logs are sent to the stdout. [Default: Info]","type":"string"},"logSeveritySys":{"description":"LogSeveritySys is the log severity above which logs are sent to the syslog. Set to None for no logging to syslog. [Default: Info]","type":"string"},"maxIpsetSize":{"type":"integer","format":"int32"},"metadataAddr":{"description":"MetadataAddr is the IP address or domain name of the server that can answer VM queries for cloud-init metadata. In OpenStack, this corresponds to the machine running nova-api (or in Ubuntu, nova-api-metadata). A value of none (case insensitive) means that Felix should not set up any NAT rule for the metadata path. [Default: 127.0.0.1]","type":"string"},"metadataPort":{"description":"MetadataPort is the port of the metadata server. This, combined with global.MetadataAddr (if not 'None'), is used to set up a NAT rule, from 169.254.169.254:80 to MetadataAddr:MetadataPort. In most cases this should not need to be changed [Default: 8775].","type":"integer","format":"int32"},"mtuIfacePattern":{"description":"MTUIfacePattern is a regular expression that controls which interfaces Felix should scan in order to calculate the host's MTU. This should not match workload interfaces (usually named cali...).","type":"string"},"natOutgoingAddress":{"description":"NATOutgoingAddress specifies an address to use when performing source NAT for traffic in a natOutgoing pool that is leaving the network. By default the address used is an address on the interface the traffic is leaving on (ie it uses the iptables MASQUERADE target)","type":"string"},"natPortRange":{"description":"NATPortRange specifies the range of ports that is used for port mapping when doing outgoing NAT. When unset the default behavior of the network stack is used.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Port"},"netlinkTimeout":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"nfNetlinkBufSize":{"type":"string"},"openstackRegion":{"description":"OpenstackRegion is the name of the region that a particular Felix belongs to. In a multi-region Calico/OpenStack deployment, this must be configured somehow for each Felix (here in the datamodel, or in felix.cfg or the environment on each compute node), and must match the [calico] openstack_region value configured in neutron.conf on each node. [Default: Empty]","type":"string"},"policySyncPathPrefix":{"description":"PolicySyncPathPrefix is used to by Felix to communicate policy changes to external services, like Application layer policy. [Default: Empty]","type":"string"},"pickleGoMetricsEnabled":{"description":"PrometheusGoMetricsEnabled disables Go runtime metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. [Default: true]","type":"boolean"},"pickleMetricsCAFile":{"type":"string"},"pickleMetricsCertFile":{"description":"TLS credentials for this port.","type":"string"},"pickleMetricsEnabled":{"description":"PrometheusMetricsEnabled enables the Prometheus metrics server in Felix if set to true. [Default: false]","type":"boolean"},"pickleMetricsHost":{"description":"PrometheusMetricsHost is the host that the Prometheus metrics server should bind to. [Default: empty]","type":"string"},"pickleMetricsKeyFile":{"type":"string"},"pickleMetricsPort":{"description":"PrometheusMetricsPort is the TCP port that the Prometheus metrics server should bind to. [Default: 9091]","type":"integer","format":"int32"},"pickleProcessMetricsEnabled":{"description":"PrometheusProcessMetricsEnabled disables process metrics collection, which the Prometheus client does by default, when set to false. This reduces the number of metrics reported, reducing Prometheus load. [Default: true]","type":"boolean"},"pickleReporterCAFile":{"type":"string"},"pickleReporterCertFile":{"type":"string"},"pickleReporterEnabled":{"description":"Felix Denied Packet Metrics configuration parameters.","type":"boolean"},"pickleReporterKeyFile":{"type":"string"},"pickleReporterPort":{"type":"integer","format":"int32"},"removeExternalRoutes":{"description":"Whether or not to remove device routes that have not been programmed by Felix. Disabling this will allow external applications to also add device routes. This is enabled by default which means we will remove externally added routes.","type":"boolean"},"reportingInterval":{"description":"ReportingInterval is the interval at which Felix reports its status into the datastore or 0 to disable. Must be non-zero in OpenStack deployments. [Default: 30s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"reportingTTL":{"description":"ReportingTTL is the time-to-live setting for process-wide status reports. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"routeRefreshInterval":{"description":"RouteRefreshInterval is the period at which Felix re-checks the routes in the dataplane to ensure that no other process has accidentally broken Calico's rules. Set to 0 to disable route refresh. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"routeSource":{"description":"RouteSource configures where Felix gets its routing information. - WorkloadIPs: use workload endpoints to construct routes. - CalicoIPAM: the default - use IPAM data to construct routes.","type":"string"},"routeTableRange":{"description":"Calico programs additional Linux route tables for various purposes. RouteTableRange specifies the indices of the route tables that Calico should use.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.RouteTableRange"},"serviceLoopPrevention":{"description":"When service IP advertisement is enabled, prevent routing loops to service IPs that are not in use, by dropping or rejecting packets that do not get DNAT'd by kube-proxy. Unless set to \"Disabled\", in which case such routing loops continue to be allowed. [Default: Drop]","type":"string"},"sidecarAccelerationEnabled":{"description":"SidecarAccelerationEnabled enables experimental sidecar acceleration [Default: false]","type":"boolean"},"statsDumpFilePath":{"type":"string"},"syslogReporterAddress":{"type":"string"},"syslogReporterNetwork":{"type":"string"},"usageReportingEnabled":{"description":"UsageReportingEnabled reports anonymous Calico version number and cluster size to projectcalico.org. Logs warnings returned by the usage server. For example, if a significant security vulnerability has been discovered in the version of Calico being used. [Default: true]","type":"boolean"},"usageReportingInitialDelay":{"description":"UsageReportingInitialDelay controls the minimum delay before Felix makes a report. [Default: 300s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"usageReportingInterval":{"description":"UsageReportingInterval controls the interval at which Felix makes reports. [Default: 86400s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"useInternalDataplaneDriver":{"type":"boolean"},"vxlanEnabled":{"type":"boolean"},"vxlanMTU":{"description":"VXLANMTU is the MTU to set on the tunnel device. See Configuring MTU [Default: 1440]","type":"integer","format":"int32"},"vxlanPort":{"type":"integer","format":"int32"},"vxlanVNI":{"type":"integer","format":"int32"},"windowsFlowLogsFileDirectory":{"description":"WindowsFlowLogsFileDirectory sets the directory where flow logs files are stored on Windows nodes. [Default: \"c:\\TigeraCalico\\flowlogs\"].","type":"string"},"windowsFlowLogsPositionFilePath":{"description":"WindowsFlowLogsPositionFilePath is used to specify the position of the external pipeline that reads flow logs on Windows nodes. [Default: \"c:\\TigeraCalico\\flowlogs\\flows.log.pos\"]. This parameter only takes effect when FlowLogsDynamicAggregationEnabled is set to true.","type":"string"},"windowsNetworkName":{"description":"WindowsNetworkName specifies which Windows HNS networks Felix should operate on. The default is to match networks that start with \"calico\". Supports regular expression syntax.","type":"string"},"windowsStatsDumpFilePath":{"description":"WindowsStatsDumpFilePath is used to specify the path of the stats dump file on Windows nodes. [Default: \"c:\\TigeraCalico\\stats\\dump\"]","type":"string"},"wireguardEnabled":{"description":"WireguardEnabled controls whether Wireguard is enabled. [Default: false]","type":"boolean"},"wireguardInterfaceName":{"description":"WireguardInterfaceName specifies the name to use for the Wireguard interface. [Default: wg.calico]","type":"string"},"wireguardListeningPort":{"description":"WireguardListeningPort controls the listening port used by Wireguard. [Default: 51820]","type":"integer","format":"int32"},"wireguardMTU":{"description":"WireguardMTU controls the MTU on the Wireguard interface. See Configuring MTU [Default: 1420]","type":"integer","format":"int32"},"wireguardRoutingRulePriority":{"description":"WireguardRoutingRulePriority controls the priority value to use for the Wireguard routing rule. [Default: 99]","type":"integer","format":"int32"},"xdpEnabled":{"description":"XDPEnabled enables XDP acceleration for suitable untracked incoming deny rules. [Default: true]","type":"boolean"},"xdpRefreshInterval":{"description":"XDPRefreshInterval is the period at which Felix re-checks all XDP state to ensure that no other process has accidentally broken Calico's BPF maps or attached programs. Set to 0 to disable XDP refresh. [Default: 90s]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertSpec":{"type":"object","required":["description","severity","dataSet"],"properties":{"aggregateBy":{"type":"array","items":{"type":"string"}},"condition":{"type":"string"},"dataSet":{"type":"string"},"description":{"type":"string"},"field":{"type":"string"},"lookback":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"metric":{"type":"string"},"period":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"query":{"type":"string"},"severity":{"type":"integer","format":"int32"},"summary":{"type":"string"},"threshold":{"type":"number","format":"double"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertStatus":{"type":"object","required":["active","healthy"],"properties":{"active":{"type":"boolean"},"errorConditions":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ErrorCondition"}},"executionState":{"type":"string"},"healthy":{"type":"boolean"},"lastEvent":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"lastExecuted":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"lastUpdate":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkPolicySpec":{"type":"object","properties":{"applyOnForward":{"description":"ApplyOnForward indicates to apply the rules in this policy on forward traffic.","type":"boolean"},"doNotTrack":{"description":"DoNotTrack indicates whether packets matched by the rules in this policy should go through the data plane's connection tracking, such as Linux conntrack. If True, the rules in this policy are applied before any data plane connection tracking, and packets allowed by this policy are marked as not to be tracked.","type":"boolean"},"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"namespaceSelector":{"description":"NamespaceSelector is an optional field for an expression used to select a pod based on namespaces.","type":"string"},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"preDNAT":{"description":"PreDNAT indicates to apply the rules in this policy before any DNAT.","type":"boolean"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress rules are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSpec":{"description":"GlobalNetworkSetSpec contains the specification for a NetworkSet resource.","type":"object","properties":{"allowedEgressDomains":{"description":"The list of domain names that belong to this set and are honored in egress allow rules only. Domain names specified here only work to allow egress traffic from the cluster to external destinations. They don't work to _deny_ traffic to destinations specified by domain name, or to allow ingress traffic from _sources_ specified by domain name.","type":"array","items":{"type":"string"}},"nets":{"description":"The list of IP networks that belong to this set.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSync":{"type":"object","properties":{"labels":{"type":"object","additionalProperties":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedSpec":{"description":"GlobalThreatFeedSpec contains the specification of a GlobalThreatFeed resource.","type":"object","properties":{"content":{"description":"Content describes the kind of data the data feed provides.","type":"string"},"globalNetworkSet":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSync"},"pull":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Pull"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedStatus":{"type":"object","required":["lastSuccessfulSync","lastSuccessfulSearch","errorConditions"],"properties":{"errorConditions":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ErrorCondition"}},"lastSuccessfulSearch":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"lastSuccessfulSync":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeader":{"type":"object","required":["name"],"properties":{"name":{"type":"string"},"value":{"type":"string"},"valueFrom":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeaderSource"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeaderSource":{"type":"object","properties":{"configMapKeyRef":{"description":"Selects a key of a ConfigMap.","$ref":"#/definitions/io.k8s.api.core.v1.ConfigMapKeySelector"},"secretKeyRef":{"description":"Selects a key of a secret in the pod's namespace","$ref":"#/definitions/io.k8s.api.core.v1.SecretKeySelector"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPMatch":{"description":"HTTPMatch is an optional field that apply only to HTTP requests The Methods and Path fields are joined with AND","type":"object","properties":{"methods":{"description":"Methods is an optional field that restricts the rule to apply only to HTTP requests that use one of the listed HTTP Methods (e.g. GET, PUT, etc.) Multiple methods are OR'd together.","type":"array","items":{"type":"string"}},"paths":{"description":"Paths is an optional field that restricts the rule to apply to HTTP requests that use one of the listed HTTP Paths. Multiple paths are OR'd together. e.g: - exact: /foo - prefix: /bar NOTE: Each entry may ONLY specify either a `exact` or a `prefix` match. The validator will check for it.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPath"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPath":{"description":"HTTPPath specifies an HTTP path to match. It may be either of the form: exact: \u003cpath\u003e: which matches the path exactly or prefix: \u003cpath-prefix\u003e: which matches the path prefix","type":"object","properties":{"exact":{"type":"string"},"prefix":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPull":{"type":"object","required":["url"],"properties":{"format":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormat"},"headers":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPHeader"}},"url":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.HostEndpointSpec":{"description":"HostEndpointSpec contains the specification for a HostEndpoint resource.","type":"object","properties":{"expectedIPs":{"description":"The expected IP addresses (IPv4 and IPv6) of the endpoint. If \"InterfaceName\" is not present, Calico will look for an interface matching any of the IPs in the list and apply policy to that. Note:\n\tWhen using the selector match criteria in an ingress or egress security Policy\n\tor Profile, Calico converts the selector into a set of IP addresses. For host\n\tendpoints, the ExpectedIPs field is used for that purpose. (If only the interface\n\tname is specified, Calico does not learn the IPs of the interface for use in match\n\tcriteria.)","type":"array","items":{"type":"string"}},"interfaceName":{"description":"Either \"*\", or the name of a specific Linux interface to apply policy to; or empty. \"*\" indicates that this HostEndpoint governs all traffic to, from or through the default network namespace of the host named by the \"Node\" field; entering and leaving that namespace via any interface, including those from/to non-host-networked local workloads.\n\nIf InterfaceName is not \"*\", this HostEndpoint only governs traffic that enters or leaves the host through the specific interface named by InterfaceName, or - when InterfaceName is empty - through the specific interface that has one of the IPs in ExpectedIPs. Therefore, when InterfaceName is empty, at least one expected IP must be specified. Only external interfaces (such as \"eth0\") are supported here; it isn't possible for a HostEndpoint to protect traffic through a specific local workload interface.\n\nNote: Only some kinds of policy are implemented for \"*\" HostEndpoints; initially just pre-DNAT policy. Please check Calico documentation for the latest position.","type":"string"},"node":{"description":"The node name identifying the Calico node instance.","type":"string"},"ports":{"description":"Ports contains the endpoint's named ports, which may be referenced in security policy rules.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointPort"}},"profiles":{"description":"A list of identifiers of security Profile objects that apply to this endpoint. Each profile is applied in the order that they appear in this list. Profile rules are applied after the selector-based security policy.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ICMPFields":{"description":"ICMPFields defines structure for ICMP and NotICMP sub-struct for ICMP code and type","type":"object","properties":{"code":{"description":"Match on a specific ICMP code. If specified, the Type value must also be specified. This is a technical limitation imposed by the kernel's iptables firewall, which Calico uses to enforce the rule.","type":"integer","format":"int32"},"type":{"description":"Match on a specific ICMP type. For example a value of 8 refers to ICMP Echo Request (i.e. pings).","type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.IPPoolSpec":{"description":"IPPoolSpec contains the specification for an IPPool resource.","type":"object","required":["cidr"],"properties":{"blockSize":{"description":"The block size to use for IP address assignments from this pool. Defaults to 26 for IPv4 and 112 for IPv6.","type":"integer","format":"int32"},"cidr":{"description":"The pool CIDR.","type":"string"},"disabled":{"description":"When disabled is true, Calico IPAM will not assign addresses from this pool.","type":"boolean"},"ipip":{"description":"Deprecated: this field is only used for APIv1 backwards compatibility. Setting this field is not allowed, this field is for internal use only.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v1.IPIPConfiguration"},"ipipMode":{"description":"Contains configuration for IPIP tunneling for this pool. If not specified, then this is defaulted to \"Never\" (i.e. IPIP tunneling is disabled).","type":"string"},"nat-outgoing":{"description":"Deprecated: this field is only used for APIv1 backwards compatibility. Setting this field is not allowed, this field is for internal use only.","type":"boolean"},"natOutgoing":{"description":"When nat-outgoing is true, packets sent from Calico networked containers in this pool to destinations outside of this pool will be masqueraded.","type":"boolean"},"nodeSelector":{"description":"Allows IPPool to allocate for a specific node by label selector.","type":"string"},"vxlanMode":{"description":"Contains configuration for VXLAN tunneling for this pool. If not specified, then this is defaulted to \"Never\" (i.e. VXLAN tunneling is disabled).","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationSpec":{"description":"KubeControllersConfigurationSpec contains the values of the Kubernetes controllers configuration.","type":"object","required":["controllers"],"properties":{"controllers":{"description":"Controllers enables and configures individual Kubernetes controllers","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ControllersConfig"},"etcdV3CompactionPeriod":{"description":"EtcdV3CompactionPeriod is the period between etcdv3 compaction requests. Set to 0 to disable. [Default: 10m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"healthChecks":{"description":"HealthChecks enables or disables support for health checks [Default: Enabled]","type":"string"},"logSeverityScreen":{"description":"LogSeverityScreen is the log severity above which logs are sent to the stdout. [Default: Info]","type":"string"},"pickleMetricsPort":{"description":"PrometheusMetricsPort is the TCP port that the Prometheus metrics server should bind to. Set to 0 to disable. [Default: 9094]","type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationStatus":{"description":"KubeControllersConfigurationStatus represents the status of the configuration. It's useful for admins to be able to see the actual config that was applied, which can be modified by environment variables on the kube-controllers process.","type":"object","properties":{"environmentVars":{"description":"EnvironmentVars contains the environment variables on the kube-controllers that influenced the RunningConfig.","type":"object","additionalProperties":{"type":"string"}},"runningConfig":{"description":"RunningConfig contains the effective config that is running in the kube-controllers pod, after merging the API resource with any environment variables.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationSpec"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeySpec":{"description":"LicenseKeySpec contains the license key itself.","type":"object","required":["token"],"properties":{"certificate":{"description":"Certificate is used to validate the token.","type":"string"},"token":{"description":"Token is the JWT containing the license claims","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeyStatus":{"description":"LicenseKeyStatus contains the license key information.","type":"object","properties":{"expiry":{"description":"Expiry is the expiry date of License","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"features":{"description":"List of features that are available via the applied license","type":"array","items":{"type":"string"}},"maxnodes":{"description":"Maximum Number of Allowed Nodes","type":"integer","format":"int32"},"package":{"description":"License package defines type of Calico license that is being enforced","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterSpec":{"description":"ManagedClusterSpec contains the specification of a ManagedCluster resource.","type":"object","properties":{"installationManifest":{"description":"Field to store dynamically generated manifest for installing component into the actual application cluster corresponding to this Managed Cluster","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatus":{"type":"object","properties":{"conditions":{"type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatusCondition"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatusCondition":{"description":"Condition contains various status information","type":"object","required":["status","type"],"properties":{"message":{"type":"string"},"reason":{"type":"string"},"status":{"type":"string"},"type":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NamesAndLabelsMatch":{"description":"NamesAndLabelsMatch is used to specify resource matches using both label and name selection.","type":"object","properties":{"names":{"description":"Names is an optional field that specifies a set of resources by name.","type":"array","items":{"type":"string"}},"selector":{"description":"Selector is an optional field that selects a set of resources by label. If both Names and Selector are specified then they are AND'ed.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NamespaceControllerConfig":{"description":"NamespaceControllerConfig configures the service account controller, which syncs Kubernetes service accounts to Calico profiles (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkPolicySpec":{"type":"object","properties":{"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkSetSpec":{"description":"NetworkSetSpec contains the specification for a NetworkSet resource.","type":"object","properties":{"allowedEgressDomains":{"description":"The list of domain names that belong to this set and are honored in egress allow rules only. Domain names specified here only work to allow egress traffic from the cluster to external destinations. They don't work to _deny_ traffic to destinations specified by domain name, or to allow ingress traffic from _sources_ specified by domain name.","type":"array","items":{"type":"string"}},"nets":{"description":"The list of IP networks that belong to this set.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.NodeControllerConfig":{"description":"NodeControllerConfig configures the node controller, which automatically cleans up configuration for nodes that no longer exist. Optionally, it can create host endpoints for all Kubernetes nodes.","type":"object","properties":{"hostEndpoint":{"description":"HostEndpoint controls syncing nodes to host endpoints. Disabled by default, set to nil to disable.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AutoHostEndpointConfig"},"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"},"syncLabels":{"description":"SyncLabels controls whether to copy Kubernetes node labels to Calico nodes. [Default: Enabled]","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.PacketCaptureSpec":{"description":"PacketCaptureSpec contains the values of the packet capture.","type":"object","properties":{"selector":{"description":"The selector is an expression used to pick out the endpoints that the policy should be applied to. The selector will only match endpoints in the same namespace as the PacketCapture resource.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.PolicyControllerConfig":{"description":"PolicyControllerConfig configures the network policy controller, which syncs Kubernetes policies to Calico policies (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.PrefixAdvertisement":{"description":"PrefixAdvertisement configures advertisement properties for the specified CIDR.","type":"object","properties":{"cidr":{"description":"CIDR for which properties should be advertised.","type":"string"},"communities":{"description":"Communities can be list of either community names already defined in `Specs.Communities` or community value of format `aa:nn` or `aa:nn:mm`. For standard community use `aa:nn` format, where `aa` and `nn` are 16 bit number. For large community use `aa:nn:mm` format, where `aa`, `nn` and `mm` are 32 bit number. Where,`aa` is an AS Number, `nn` and `mm` are per-AS identifier.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ProfileSpec":{"description":"ProfileSpec contains the specification for a security Profile resource.","type":"object","properties":{"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"egressGateway":{"description":"Egress control.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EgressSpec"},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"labelsToApply":{"description":"An option set of labels to apply to each endpoint (in addition to their own labels) referencing this profile. If labels configured on the endpoint have keys matching those labels inherited from the profile, the endpoint label values take precedence.","type":"object","additionalProperties":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ProtoPort":{"description":"ProtoPort is combination of protocol and port, both must be specified.","type":"object","required":["protocol","port"],"properties":{"port":{"type":"integer","format":"int32"},"protocol":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.Pull":{"type":"object","required":["http"],"properties":{"http":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPPull"},"period":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.RemoteClusterConfigurationSpec":{"description":"RemoteClusterConfigurationSpec contains the values of describing the cluster.","type":"object","properties":{"clusterAccessSecret":{"description":"Specifies a Secret to read for the RemoteClusterconfiguration. If defined all datastore configuration in this struct will be cleared and overwritten with the appropriate fields in the Secret.","$ref":"#/definitions/io.k8s.api.core.v1.ObjectReference"},"datastoreType":{"description":"Indicates the datastore to use. If unspecified, defaults to etcdv3","type":"string"},"etcdCACert":{"type":"string"},"etcdCACertFile":{"description":"Path to the etcd Certificate Authority file. Valid if DatastoreType is etcdv3.","type":"string"},"etcdCert":{"type":"string"},"etcdCertFile":{"description":"Path to the etcd client certificate. Valid if DatastoreType is etcdv3.","type":"string"},"etcdEndpoints":{"description":"A comma separated list of etcd endpoints. Valid if DatastoreType is etcdv3. [Default: ]","type":"string"},"etcdKey":{"description":"These config file parameters are to support inline certificates, keys and CA / Trusted certificate.","type":"string"},"etcdKeyFile":{"description":"Path to the etcd key file. Valid if DatastoreType is etcdv3.","type":"string"},"etcdPassword":{"description":"Password for the given user name. Valid if DatastoreType is etcdv3.","type":"string"},"etcdUsername":{"description":"User name for RBAC. Valid if DatastoreType is etcdv3.","type":"string"},"k8sAPIEndpoint":{"description":"Location of the Kubernetes API. Not required if using kubeconfig. Valid if DatastoreType is kubernetes.","type":"string"},"k8sAPIToken":{"description":"Token to be used for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"k8sCAFile":{"description":"Location of a CA for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"k8sCertFile":{"description":"Location of a client certificate for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"k8sInsecureSkipTLSVerify":{"type":"boolean"},"k8sKeyFile":{"description":"Location of a client key for accessing the Kubernetes API. Valid if DatastoreType is kubernetes.","type":"string"},"kubeconfig":{"description":"When using the Kubernetes datastore, the location of a kubeconfig file. Valid if DatastoreType is kubernetes.","type":"string"},"kubeconfigInline":{"description":"This is an alternative to Kubeconfig and if specified overrides Kubeconfig. This contains the contents that would normally be in the file pointed at by Kubeconfig.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportJob":{"description":"ReportJob contains","type":"object","required":["start","end","job"],"properties":{"end":{"description":"The end time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"job":{"description":"A reference to the report creation job if known.","$ref":"#/definitions/io.k8s.api.core.v1.ObjectReference"},"start":{"description":"The start time of the report.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportSpec":{"description":"ReportSpec contains the values of the GlobalReport.","type":"object","required":["reportType"],"properties":{"cis":{"description":"This field contain all the parameters for configuring a CIS benchmark report.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CISBenchmarkParams"},"endpoints":{"description":"Endpoints is used to specify which endpoints are in-scope and stored in the generated report data. Only used if endpoints data and/or audit logs are gathered in the report. If omitted, treated as everything in-scope.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EndpointsSelection"},"jobNodeSelector":{"description":"The node selector used to specify which nodes the report job may be scheduled on.","type":"object","additionalProperties":{"type":"string"}},"reportType":{"description":"The name of the report type.","type":"string"},"schedule":{"description":"The report schedule specified in cron format. This specifies both the start and end times of each report, where the end time of one report becomes the start time of the next report. Separate jobs are created to generate a report, and the job generates the report data from archived audit and traffic data. To ensure this data is actually archived, the jobs to generate each report starts at a configurable time *after* the end time of the report that is being generated. The default job start delay is 30m, but is configurable through the compliance-controller environments. The cron format has minute accuracy, but only up to two values may be configured for the minute column which means you may only have at most two reports for each hour period.","type":"string"},"suspend":{"description":"This flag tells the controller to suspend subsequent jobs for generating reports, it does not apply to already started jobs. If jobs are resumed then the controller will start creating jobs for any reports that were missed while the job was suspended.","type":"boolean"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportStatus":{"description":"ReportStatus contains the status of the automated report generation.","type":"object","properties":{"activeReportJobs":{"description":"The set of active report jobs.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportJob"}},"lastFailedReportJobs":{"description":"The configured report jobs that have failed.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CompletedReportJob"}},"lastScheduledReportJob":{"description":"The last scheduled report job.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportJob"},"lastSuccessfulReportJobs":{"description":"The configured report jobs that have completed successfully.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.CompletedReportJob"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTemplate":{"description":"ReportTemplate defines a template used to render a report into downloadable or UI compatible format.","type":"object","properties":{"description":{"description":"A user-facing description of the template.","type":"string"},"name":{"description":"The name of this template. This should be unique across all template names within a ReportType. This will be used by the UI as the suffix of the downloadable file name.","type":"string"},"template":{"description":"The base-64 encoded go template used to render the report data.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTypeSpec":{"description":"ReportTypeSpec contains the various templates, and configuration used to render a specific type of report.","type":"object","properties":{"auditEventsSelection":{"description":"What audit log data should be included in the report. If not specified, the report will contain no audit log data. The selection may be further filtered by the Report.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuditEventsSelection"},"downloadTemplates":{"description":"The set of templates used to render the report for downloads.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTemplate"}},"includeCISBenchmarkData":{"description":"Whether to include the full cis benchmark test results in the report.","type":"boolean"},"includeEndpointData":{"description":"Whether to include endpoint data in the report. The actual endpoints included may be filtered by the Report, but will otherwise contain the full set of endpoints.","type":"boolean"},"includeEndpointFlowLogData":{"description":"Whether to include endpoint-to-endpoint flow log data in the report.","type":"boolean"},"uiSummaryTemplate":{"description":"The summary template, explicitly used by the UI to render a summary version of the report. This should render to json containing a sets of widgets that the UI can use to render the summary. The rendered data is returned on the list query of the reports.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTemplate"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.RouteTableRange":{"type":"object","required":["min","max"],"properties":{"max":{"type":"integer","format":"int32"},"min":{"type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.Rule":{"description":"A Rule encapsulates a set of match criteria and an action. Both selector-based security Policy and security Profiles reference rules - separated out as a list of rules for both ingress and egress packet matching.\n\nEach positive match criteria has a negated version, prefixed with \"Not\". All the match criteria within a rule must be satisfied for a packet to match. A single rule can contain the positive and negative version of a match and both must be satisfied for the rule to match.","type":"object","required":["action"],"properties":{"action":{"type":"string"},"destination":{"description":"Destination contains the match criteria that apply to destination entity.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EntityRule"},"http":{"description":"HTTP contains match criteria that apply to HTTP requests.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HTTPMatch"},"icmp":{"description":"ICMP is an optional field that restricts the rule to apply to a specific type and code of ICMP traffic. This should only be specified if the Protocol field is set to \"ICMP\" or \"ICMPv6\".","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ICMPFields"},"ipVersion":{"description":"IPVersion is an optional field that restricts the rule to only match a specific IP version.","type":"integer","format":"int32"},"metadata":{"description":"Metadata contains additional information for this rule","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.RuleMetadata"},"notICMP":{"description":"NotICMP is the negated version of the ICMP field.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ICMPFields"},"notProtocol":{"description":"NotProtocol is the negated version of the Protocol field.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Protocol"},"protocol":{"description":"Protocol is an optional field that restricts the rule to only apply to traffic of a specific IP protocol. Required if any of the EntityRules contain Ports (because ports only apply to certain protocols).\n\nMust be one of these string values: \"TCP\", \"UDP\", \"ICMP\", \"ICMPv6\", \"SCTP\", \"UDPLite\" or an integer in the range 1-255.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.numorstring.Protocol"},"source":{"description":"Source contains the match criteria that apply to source entity.","$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.EntityRule"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.RuleMetadata":{"type":"object","properties":{"annotations":{"description":"Annotations is a set of key value pairs that give extra information about the rule","type":"object","additionalProperties":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountControllerConfig":{"description":"ServiceAccountControllerConfig configures the service account controller, which syncs Kubernetes service accounts to Calico profiles (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceAccountMatch":{"type":"object","properties":{"names":{"description":"Names is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) a pod running as a service account whose name is in the list.","type":"array","items":{"type":"string"}},"selector":{"description":"Selector is an optional field that restricts the rule to only apply to traffic that originates from (or terminates at) a pod running as a service account that matches the given label selector. If both Names and Selector are specified then they are AND'ed.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceClusterIPBlock":{"description":"ServiceClusterIPBlock represents a single allowed ClusterIP CIDR block.","type":"object","properties":{"cidr":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceExternalIPBlock":{"description":"ServiceExternalIPBlock represents a single allowed External IP CIDR block.","type":"object","properties":{"cidr":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ServiceLoadBalancerIPBlock":{"description":"ServiceLoadBalancerIPBlock represents a single allowed LoadBalancer IP CIDR block.","type":"object","properties":{"cidr":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.StagedGlobalNetworkPolicySpec":{"type":"object","properties":{"applyOnForward":{"description":"ApplyOnForward indicates to apply the rules in this policy on forward traffic.","type":"boolean"},"doNotTrack":{"description":"DoNotTrack indicates whether packets matched by the rules in this policy should go through the data plane's connection tracking, such as Linux conntrack. If True, the rules in this policy are applied before any data plane connection tracking, and packets allowed by this policy are marked as not to be tracked.","type":"boolean"},"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"namespaceSelector":{"description":"NamespaceSelector is an optional field for an expression used to select a pod based on namespaces.","type":"string"},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"preDNAT":{"description":"PreDNAT indicates to apply the rules in this policy before any DNAT.","type":"boolean"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"stagedAction":{"description":"The staged action. If this is omitted, the default is Set.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress rules are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.StagedKubernetesNetworkPolicySpec":{"type":"object","properties":{"egress":{"description":"List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyEgressRule"}},"ingress":{"description":"List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod's local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyIngressRule"}},"podSelector":{"description":"Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector"},"policyTypes":{"description":"List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ \"Egress\" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include \"Egress\" (since such a policy would not include an Egress section and would otherwise default to just [ \"Ingress\" ]). This field is beta-level in 1.8","type":"array","items":{"type":"string"}},"stagedAction":{"description":"The staged action. If this is omitted, the default is Set.","type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.StagedNetworkPolicySpec":{"type":"object","properties":{"egress":{"description":"The ordered set of egress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"ingress":{"description":"The ordered set of ingress rules. Each rule contains a set of packet match criteria and a corresponding action to apply.","type":"array","items":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.Rule"}},"order":{"description":"Order is an optional field that specifies the order in which the policy is applied. Policies with higher \"order\" are applied after those with lower order within the same tier. If the order is omitted, it may be considered to be \"infinite\" - i.e. the policy will be applied last. Policies with identical order will be applied in alphanumerical order based on the Policy \"Name\" within the tier.","type":"number","format":"double"},"selector":{"description":"The selector is an expression used to pick pick out the endpoints that the policy should be applied to.\n\nSelector expressions follow this syntax:\n\n\tlabel == \"string_literal\" -\u003e comparison, e.g. my_label == \"foo bar\"\n\tlabel != \"string_literal\" -\u003e not equal; also matches if label is not present\n\tlabel in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is one of \"a\", \"b\", \"c\"\n\tlabel not in { \"a\", \"b\", \"c\", ... } -\u003e true if the value of label X is not one of \"a\", \"b\", \"c\"\n\thas(label_name) -\u003e True if that label is present\n\t! expr -\u003e negation of expr\n\texpr \u0026\u0026 expr -\u003e Short-circuit and\n\texpr || expr -\u003e Short-circuit or\n\t( expr ) -\u003e parens for grouping\n\tall() or the empty selector -\u003e matches all endpoints.\n\nLabel names are allowed to contain alphanumerics, -, _ and /. String literals are more permissive but they do not support escape characters.\n\nExamples (with made-up labels):\n\n\ttype == \"webserver\" \u0026\u0026 deployment == \"prod\"\n\ttype in {\"frontend\", \"backend\"}\n\tdeployment != \"dev\"\n\t! has(label_name)","type":"string"},"serviceAccountSelector":{"description":"ServiceAccountSelector is an optional field for an expression used to select a pod based on service accounts.","type":"string"},"stagedAction":{"description":"The staged action. If this is omitted, the default is Set.","type":"string"},"tier":{"description":"The name of the tier that this policy belongs to. If this is omitted, the default tier (name is \"default\") is assumed. The specified tier must exist in order to create security policies within the tier, the \"default\" tier is created automatically if it does not exist, this means for deployments requiring only a single Tier, the tier name may be omitted on all policy management requests.","type":"string"},"types":{"description":"Types indicates whether this policy applies to ingress, or to egress, or to both. When not explicitly specified (and so the value on creation is empty or nil), Calico defaults Types according to what Ingress and Egress are present in the policy. The default is:\n\n- [ PolicyTypeIngress ], if there are no Egress rules (including the case where there are\n also no Ingress rules)\n\n- [ PolicyTypeEgress ], if there are Egress rules but no Ingress rules\n\n- [ PolicyTypeIngress, PolicyTypeEgress ], if there are both Ingress and Egress rules.\n\nWhen the policy is read back again, Types will always be one of these values, never empty or nil.","type":"array","items":{"type":"string"}}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormat":{"type":"object","properties":{"csv":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatCSV"},"json":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatJSON"},"newlineDelimited":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatNewlineDelimited"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatCSV":{"type":"object","properties":{"columnDelimiter":{"type":"string"},"commentDelimiter":{"type":"string"},"disableRecordSizeValidation":{"type":"boolean"},"fieldName":{"type":"string"},"fieldNum":{"type":"integer","format":"int32"},"header":{"type":"boolean"},"recordSize":{"type":"integer","format":"int32"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatJSON":{"type":"object","properties":{"path":{"type":"string"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.ThreatFeedFormatNewlineDelimited":{"type":"object"},"com.github.projectcalico.libcalico-go.lib.apis.v3.TierSpec":{"description":"TierSpec contains the specification for a security policy tier resource.","type":"object","properties":{"order":{"description":"Order is an optional field that specifies the order in which the tier is applied. Tiers with higher \"order\" are applied after those with lower order. If the order is omitted, it may be considered to be \"infinite\" - i.e. the tier will be applied last. Tiers with identical order will be applied in alphanumerical order based on the Tier \"Name\".","type":"number","format":"double"}}},"com.github.projectcalico.libcalico-go.lib.apis.v3.WorkloadEndpointControllerConfig":{"description":"WorkloadEndpointControllerConfig configures the workload endpoint controller, which syncs Kubernetes labels to Calico workload endpoints (only used for etcdv3 datastore).","type":"object","properties":{"reconcilerPeriod":{"description":"ReconcilerPeriod is the period to perform reconciliation with the Calico datastore. [Default: 5m]","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Duration"}}},"com.github.projectcalico.libcalico-go.lib.numorstring.Port":{"type":"string","format":"int-or-string"},"com.github.projectcalico.libcalico-go.lib.numorstring.Protocol":{"type":"string","format":"int-or-string"},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthenticationReview":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthenticationReviewStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"AuthenticationReview","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.AuthorizationReview":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.AuthorizationReviewStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"AuthorizationReview","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.BGPConfigurationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfigurationList":{"description":"BGPConfigurationList is a list of BGPConfiguration resources.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.BGPPeerSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPPeer","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeerList":{"description":"BGPPeerList is a list of BGPPeer resources.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.BGPPeer"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"BGPPeerList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ClusterInformationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ClusterInformation","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformationList":{"description":"ClusterInformationList is a list of ClusterInformation objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ClusterInformation"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ClusterInformationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.FelixConfigurationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"FelixConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfigurationList":{"description":"FelixConfigurationList contains a list of FelixConfiguration object.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.FelixConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"FelixConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlert","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertList":{"description":"GlobalAlertList is a list of GlobalAlert objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlert"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlertList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalAlertSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlertTemplate","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplateList":{"description":"GlobalAlertTemplateList is a list of GlobalAlertTemplate objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalAlertTemplate"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalAlertTemplateList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicyList":{"description":"GlobalNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalNetworkSetSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkSet","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSetList":{"description":"GlobalNetworkSetList is a list of NetworkSet objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalNetworkSet"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalNetworkSetList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReport","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportList":{"description":"GlobalReportList is a list of GlobalReport objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReport"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReportList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ReportTypeSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReportType","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportTypeList":{"description":"GlobalReportTypeList is a list of GlobalReportType objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalReportType"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalReportTypeList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.GlobalThreatFeedStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalThreatFeed","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeedList":{"description":"GlobalThreatFeedList is a list of GlobalThreatFeed objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.GlobalThreatFeed"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"GlobalThreatFeedList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.HostEndpointSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"HostEndpoint","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpointList":{"description":"HostEndpointList is a list of HostEndpoint objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.HostEndpoint"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"HostEndpointList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.IPPoolSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"IPPool","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPoolList":{"description":"IPPoolList contains a list of IPPool resources.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.IPPool"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"IPPoolList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.KubeControllersConfigurationStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"KubeControllersConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfigurationList":{"description":"KubeControllersConfigurationList contains a list of KubeControllersConfiguration object.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.KubeControllersConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"KubeControllersConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeySpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.LicenseKeyStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"LicenseKey","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKeyList":{"description":"LicenseKeyList is a list of license objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.LicenseKey"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"LicenseKeyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterSpec"},"status":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ManagedClusterStatus"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ManagedCluster","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedClusterList":{"description":"ManagedClusterList is a list of ManagedCluster objects (used for multi-cluster management).","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ManagedCluster"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ManagedClusterList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicyList":{"description":"NetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.NetworkSetSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkSet","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSetList":{"description":"NetworkSetList is a list of NetworkSet objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.NetworkSet"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"NetworkSetList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.PacketCaptureSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"PacketCapture","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCaptureList":{"description":"PacketCaptureList is a list of PacketCapture objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.PacketCapture"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"PacketCaptureList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.ProfileSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"Profile","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.ProfileList":{"description":"ProfileList is a list of Profile objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Profile"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"ProfileList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.RemoteClusterConfigurationSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"RemoteClusterConfiguration","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfigurationList":{"description":"RemoteClusterConfigurationList is a list of RemoteClusterConfiguration objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.RemoteClusterConfiguration"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"RemoteClusterConfigurationList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.StagedGlobalNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedGlobalNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicyList":{"description":"StagedGlobalNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedGlobalNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedGlobalNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.StagedKubernetesNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedKubernetesNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicyList":{"description":"StagedKubernetesNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedKubernetesNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedKubernetesNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.StagedNetworkPolicySpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedNetworkPolicy","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicyList":{"description":"StagedNetworkPolicyList is a list of Policy objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.StagedNetworkPolicy"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"StagedNetworkPolicyList","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier":{"type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta"},"spec":{"$ref":"#/definitions/com.github.projectcalico.libcalico-go.lib.apis.v3.TierSpec"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"Tier","version":"v3"}]},"com.github.tigera.apiserver.pkg.apis.projectcalico.v3.TierList":{"description":"TierList is a list of Tier objects.","type":"object","required":["items"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"items":{"type":"array","items":{"$ref":"#/definitions/com.github.tigera.apiserver.pkg.apis.projectcalico.v3.Tier"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"metadata":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"}},"x-kubernetes-group-version-kind":[{"group":"projectcalico.org","kind":"TierList","version":"v3"}]},"io.k8s.api.core.v1.ConfigMapKeySelector":{"description":"Selects a key from a ConfigMap.","type":"object","required":["key"],"properties":{"key":{"description":"The key to select.","type":"string"},"name":{"description":"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names","type":"string"},"optional":{"description":"Specify whether the ConfigMap or its key must be defined","type":"boolean"}}},"io.k8s.api.core.v1.ObjectReference":{"description":"ObjectReference contains enough information to let you inspect or modify the referred object.","type":"object","properties":{"apiVersion":{"description":"API version of the referent.","type":"string"},"fieldPath":{"description":"If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: \"spec.containers{name}\" (where \"name\" refers to the name of the container that triggered the event) or if no container name is specified \"spec.containers[2]\" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.","type":"string"},"kind":{"description":"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names","type":"string"},"namespace":{"description":"Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/","type":"string"},"resourceVersion":{"description":"Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency","type":"string"},"uid":{"description":"UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids","type":"string"}}},"io.k8s.api.core.v1.SecretKeySelector":{"description":"SecretKeySelector selects a key of a Secret.","type":"object","required":["key"],"properties":{"key":{"description":"The key of the secret to select from. Must be a valid secret key.","type":"string"},"name":{"description":"Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names","type":"string"},"optional":{"description":"Specify whether the Secret or its key must be defined","type":"boolean"}}},"io.k8s.api.networking.v1.IPBlock":{"description":"IPBlock describes a particular CIDR (Ex. \"192.168.1.1/24\",\"2001:db9::/64\") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.","type":"object","required":["cidr"],"properties":{"cidr":{"description":"CIDR is a string representing the IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\"","type":"string"},"except":{"description":"Except is a slice of CIDRs that should not be included within an IP Block Valid examples are \"192.168.1.1/24\" or \"2001:db9::/64\" Except values will be rejected if they are outside the CIDR range","type":"array","items":{"type":"string"}}}},"io.k8s.api.networking.v1.NetworkPolicyEgressRule":{"description":"NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8","type":"object","properties":{"ports":{"description":"List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPort"}},"to":{"description":"List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPeer"}}}},"io.k8s.api.networking.v1.NetworkPolicyIngressRule":{"description":"NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.","type":"object","properties":{"from":{"description":"List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the from list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPeer"}},"ports":{"description":"List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.","type":"array","items":{"$ref":"#/definitions/io.k8s.api.networking.v1.NetworkPolicyPort"}}}},"io.k8s.api.networking.v1.NetworkPolicyPeer":{"description":"NetworkPolicyPeer describes a peer to allow traffic to/from. Only certain combinations of fields are allowed","type":"object","properties":{"ipBlock":{"description":"IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.","$ref":"#/definitions/io.k8s.api.networking.v1.IPBlock"},"namespaceSelector":{"description":"Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.\n\nIf PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector"},"podSelector":{"description":"This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.\n\nIf NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy's own Namespace.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector"}}},"io.k8s.api.networking.v1.NetworkPolicyPort":{"description":"NetworkPolicyPort describes a port to allow traffic on","type":"object","properties":{"port":{"description":"The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers.","$ref":"#/definitions/io.k8s.apimachinery.pkg.util.intstr.IntOrString"},"protocol":{"description":"The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup":{"description":"APIGroup contains the name, the supported versions, and the preferred version of a group.","type":"object","required":["name","versions"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"name is the name of the group.","type":"string"},"preferredVersion":{"description":"preferredVersion is the version preferred by the API server, which probably is the storage version.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.GroupVersionForDiscovery"},"serverAddressByClientCIDRs":{"description":"a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ServerAddressByClientCIDR"}},"versions":{"description":"versions are the versions supported in this group.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.GroupVersionForDiscovery"}}},"x-kubernetes-group-version-kind":[{"group":"","kind":"APIGroup","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.APIGroupList":{"description":"APIGroupList is a list of APIGroup, to allow clients to discover the API at /apis.","type":"object","required":["groups"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"groups":{"description":"groups is a list of APIGroup.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup"}},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"APIGroupList","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.APIResource":{"description":"APIResource specifies the name of a resource and whether it is namespaced.","type":"object","required":["name","singularName","namespaced","kind","verbs"],"properties":{"categories":{"description":"categories is a list of the grouped resources this resource belongs to (e.g. 'all')","type":"array","items":{"type":"string"}},"group":{"description":"group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale\".","type":"string"},"kind":{"description":"kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')","type":"string"},"name":{"description":"name is the plural name of the resource.","type":"string"},"namespaced":{"description":"namespaced indicates if a resource is namespaced or not.","type":"boolean"},"shortNames":{"description":"shortNames is a list of suggested short names of the resource.","type":"array","items":{"type":"string"}},"singularName":{"description":"singularName is the singular name of the resource. This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.","type":"string"},"storageVersionHash":{"description":"The hash value of the storage version, the version this resource is converted to when written to the data store. Value must be treated as opaque by clients. Only equality comparison on the value is valid. This is an alpha feature and may change or be removed in the future. The field is populated by the apiserver only if the StorageVersionHash feature gate is enabled. This field will remain optional even if it graduates.","type":"string"},"verbs":{"description":"verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)","type":"array","items":{"type":"string"}},"version":{"description":"version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource's group)\".","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList":{"description":"APIResourceList is a list of APIResource, it is used to expose the name of the resources supported in a specific group and version, and if the resource is namespaced.","type":"object","required":["groupVersion","resources"],"properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"groupVersion":{"description":"groupVersion is the group and version this APIResourceList is for.","type":"string"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"resources":{"description":"resources contains the name of the resources and if they are namespaced.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResource"}}},"x-kubernetes-group-version-kind":[{"group":"","kind":"APIResourceList","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions":{"description":"DeleteOptions may be provided when deleting an API object.","type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"dryRun":{"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed","type":"array","items":{"type":"string"}},"gracePeriodSeconds":{"description":"The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.","type":"integer","format":"int64"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"orphanDependents":{"description":"Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.","type":"boolean"},"preconditions":{"description":"Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Preconditions"},"propagationPolicy":{"description":"Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.","type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"DeleteOptions","version":"v1"},{"group":"projectcalico.org","kind":"DeleteOptions","version":"v3"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.Duration":{"description":"Duration is a wrapper around time.Duration which supports correct marshaling to YAML and JSON. In particular, it marshals into strings, which can be used as map keys in json.","type":"string"},"io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1":{"description":"FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format.\n\nEach key is either a '.' representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: 'f:\u003cname\u003e', where \u003cname\u003e is the name of a field in a struct, or key in a map 'v:\u003cvalue\u003e', where \u003cvalue\u003e is the exact json formatted value of a list item 'i:\u003cindex\u003e', where \u003cindex\u003e is position of a item in a list 'k:\u003ckeys\u003e', where \u003ckeys\u003e is a map of a list item's key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set.\n\nThe exact format is defined in sigs.k8s.io/structured-merge-diff","type":"object"},"io.k8s.apimachinery.pkg.apis.meta.v1.GroupVersionForDiscovery":{"description":"GroupVersion contains the \"group/version\" and \"version\" string of a version. It is made a struct to keep extensibility.","type":"object","required":["groupVersion","version"],"properties":{"groupVersion":{"description":"groupVersion specifies the API group and version in the form \"group/version\"","type":"string"},"version":{"description":"version specifies the version in the form of \"version\". This is to save the clients the trouble of splitting the GroupVersion.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector":{"description":"A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.","type":"object","properties":{"matchExpressions":{"description":"matchExpressions is a list of label selector requirements. The requirements are ANDed.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelectorRequirement"}},"matchLabels":{"description":"matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is \"key\", the operator is \"In\", and the values array contains only \"value\". The requirements are ANDed.","type":"object","additionalProperties":{"type":"string"}}}},"io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelectorRequirement":{"description":"A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.","type":"object","required":["key","operator"],"properties":{"key":{"description":"key is the label key that the selector applies to.","type":"string","x-kubernetes-patch-merge-key":"key","x-kubernetes-patch-strategy":"merge"},"operator":{"description":"operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.","type":"string"},"values":{"description":"values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.","type":"array","items":{"type":"string"}}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta":{"description":"ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.","type":"object","properties":{"continue":{"description":"continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a consistent list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response, unless you have received this token from an error message.","type":"string"},"remainingItemCount":{"description":"remainingItemCount is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the field will be left unset and omitted during serialization. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and this field will be left unset and omitted during serialization. Servers older than v1.15 do not set this field. The intended use of the remainingItemCount is *estimating* the size of a collection. Clients should not rely on the remainingItemCount to be set or to be exact.","type":"integer","format":"int64"},"resourceVersion":{"description":"String that identifies the server's internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency","type":"string"},"selfLink":{"description":"selfLink is a URL representing this object. Populated by the system. Read-only.\n\nDEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ManagedFieldsEntry":{"description":"ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.","type":"object","properties":{"apiVersion":{"description":"APIVersion defines the version of this resource that this field set applies to. The format is \"group/version\" just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted.","type":"string"},"fieldsType":{"description":"FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: \"FieldsV1\"","type":"string"},"fieldsV1":{"description":"FieldsV1 holds the first JSON version format as described in the \"FieldsV1\" type.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1"},"manager":{"description":"Manager is an identifier of the workflow managing these fields.","type":"string"},"operation":{"description":"Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are 'Apply' and 'Update'.","type":"string"},"time":{"description":"Time is timestamp of when these fields were set. It should always be empty if Operation is 'Apply'","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta":{"description":"ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.","type":"object","properties":{"annotations":{"description":"Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations","type":"object","additionalProperties":{"type":"string"}},"clusterName":{"description":"The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.","type":"string"},"creationTimestamp":{"description":"CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.\n\nPopulated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"deletionGracePeriodSeconds":{"description":"Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.","type":"integer","format":"int64"},"deletionTimestamp":{"description":"DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested.\n\nPopulated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time"},"finalizers":{"description":"Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed. Finalizers may be processed and removed in any order. Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list.","type":"array","items":{"type":"string"},"x-kubernetes-patch-strategy":"merge"},"generateName":{"description":"GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server.\n\nIf this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).\n\nApplied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency","type":"string"},"generation":{"description":"A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.","type":"integer","format":"int64"},"labels":{"description":"Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels","type":"object","additionalProperties":{"type":"string"}},"managedFields":{"description":"ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like \"ci-cd\". The set of fields is always in the version that the workflow used when modifying the object.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ManagedFieldsEntry"}},"name":{"description":"Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names","type":"string"},"namespace":{"description":"Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the \"default\" namespace, but \"default\" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty.\n\nMust be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces","type":"string"},"ownerReferences":{"description":"List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.OwnerReference"},"x-kubernetes-patch-merge-key":"uid","x-kubernetes-patch-strategy":"merge"},"resourceVersion":{"description":"An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources.\n\nPopulated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency","type":"string"},"selfLink":{"description":"SelfLink is a URL representing this object. Populated by the system. Read-only.\n\nDEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.","type":"string"},"uid":{"description":"UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations.\n\nPopulated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.OwnerReference":{"description":"OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.","type":"object","required":["apiVersion","kind","name","uid"],"properties":{"apiVersion":{"description":"API version of the referent.","type":"string"},"blockOwnerDeletion":{"description":"If true, AND if the owner has the \"foregroundDeletion\" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs \"delete\" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.","type":"boolean"},"controller":{"description":"If true, this reference points to the managing controller.","type":"boolean"},"kind":{"description":"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names","type":"string"},"uid":{"description":"UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.Patch":{"description":"Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.","type":"object"},"io.k8s.apimachinery.pkg.apis.meta.v1.Preconditions":{"description":"Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.","type":"object","properties":{"resourceVersion":{"description":"Specifies the target ResourceVersion","type":"string"},"uid":{"description":"Specifies the target UID.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.ServerAddressByClientCIDR":{"description":"ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.","type":"object","required":["clientCIDR","serverAddress"],"properties":{"clientCIDR":{"description":"The CIDR with which clients can match their IP to figure out the server address that they should use.","type":"string"},"serverAddress":{"description":"Address of this server, suitable for a client that matches the above CIDR. This can be a hostname, hostname:port, IP or IP:port.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.Status":{"description":"Status is a return value for calls that don't return other objects.","type":"object","properties":{"apiVersion":{"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources","type":"string"},"code":{"description":"Suggested HTTP return code for this status, 0 if not set.","type":"integer","format":"int32"},"details":{"description":"Extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.StatusDetails"},"kind":{"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"message":{"description":"A human-readable description of the status of this operation.","type":"string"},"metadata":{"description":"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta"},"reason":{"description":"A machine-readable description of why this operation is in the \"Failure\" status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.","type":"string"},"status":{"description":"Status of the operation. One of: \"Success\" or \"Failure\". More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status","type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"Status","version":"v1"}]},"io.k8s.apimachinery.pkg.apis.meta.v1.StatusCause":{"description":"StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.","type":"object","properties":{"field":{"description":"The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed. Fields may appear more than once in an array of causes due to fields having multiple errors. Optional.\n\nExamples:\n \"name\" - the field \"name\" on the current resource\n \"items[0].name\" - the field \"name\" on the first array entry in \"items\"","type":"string"},"message":{"description":"A human-readable description of the cause of the error. This field may be presented as-is to a reader.","type":"string"},"reason":{"description":"A machine-readable description of the cause of the error. If this value is empty there is no information available.","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.StatusDetails":{"description":"StatusDetails is a set of additional properties that MAY be set by the server to provide additional information about a response. The Reason field of a Status object defines what attributes will be set. Clients must ignore fields that do not match the defined type of each attribute, and should assume that any attribute may be empty, invalid, or under defined.","type":"object","properties":{"causes":{"description":"The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.","type":"array","items":{"$ref":"#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.StatusCause"}},"group":{"description":"The group attribute of the resource associated with the status StatusReason.","type":"string"},"kind":{"description":"The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds","type":"string"},"name":{"description":"The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).","type":"string"},"retryAfterSeconds":{"description":"If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.","type":"integer","format":"int32"},"uid":{"description":"UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids","type":"string"}}},"io.k8s.apimachinery.pkg.apis.meta.v1.Time":{"description":"Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON. Wrappers are provided for many of the factory methods that the time package offers.","type":"string","format":"date-time"},"io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent":{"description":"Event represents a single event to a watched resource.","type":"object","required":["type","object"],"properties":{"object":{"description":"Object is:\n * If Type is Added or Modified: the new state of the object.\n * If Type is Deleted: the state of the object immediately before deletion.\n * If Type is Error: *Status is recommended; other types may make sense\n depending on context.","$ref":"#/definitions/io.k8s.apimachinery.pkg.runtime.RawExtension"},"type":{"type":"string"}},"x-kubernetes-group-version-kind":[{"group":"","kind":"WatchEvent","version":"v1"},{"group":"projectcalico.org","kind":"WatchEvent","version":"v3"}]},"io.k8s.apimachinery.pkg.runtime.RawExtension":{"description":"RawExtension is used to hold extensions in external versions.\n\nTo use this, make a field which has RawExtension as its type in your external, versioned struct, and Object in your internal struct. You also need to register your various plugin types.\n\n// Internal package: type MyAPIObject struct {\n\truntime.TypeMeta `json:\",inline\"`\n\tMyPlugin runtime.Object `json:\"myPlugin\"`\n} type PluginA struct {\n\tAOption string `json:\"aOption\"`\n}\n\n// External package: type MyAPIObject struct {\n\truntime.TypeMeta `json:\",inline\"`\n\tMyPlugin runtime.RawExtension `json:\"myPlugin\"`\n} type PluginA struct {\n\tAOption string `json:\"aOption\"`\n}\n\n// On the wire, the JSON will look something like this: {\n\t\"kind\":\"MyAPIObject\",\n\t\"apiVersion\":\"v1\",\n\t\"myPlugin\": {\n\t\t\"kind\":\"PluginA\",\n\t\t\"aOption\":\"foo\",\n\t},\n}\n\nSo what happens? Decode first uses json or yaml to unmarshal the serialized data into your external MyAPIObject. That causes the raw JSON to be stored, but not unpacked. The next step is to copy (using pkg/conversion) into the internal struct. The runtime package's DefaultScheme has conversion functions installed which will unpack the JSON stored in RawExtension, turning it into the correct object type, and storing it in the Object. (TODO: In the case where the object is of an unknown type, a runtime.Unknown object will be created and stored.)","type":"object"},"io.k8s.apimachinery.pkg.util.intstr.IntOrString":{"description":"IntOrString is a type that can hold an int32 or a string. When used in JSON or YAML marshalling and unmarshalling, it produces or consumes the inner type. This allows you to have, for example, a JSON field that can accept a name or number.","type":"string","format":"int-or-string"},"io.k8s.apimachinery.pkg.version.Info":{"description":"Info contains versioning information. how we'll want to distribute that information.","type":"object","required":["major","minor","gitVersion","gitCommit","gitTreeState","buildDate","goVersion","compiler","platform"],"properties":{"buildDate":{"type":"string"},"compiler":{"type":"string"},"gitCommit":{"type":"string"},"gitTreeState":{"type":"string"},"gitVersion":{"type":"string"},"goVersion":{"type":"string"},"major":{"type":"string"},"minor":{"type":"string"},"platform":{"type":"string"}}}}} \ No newline at end of file From e04002d6c6f652d4b01dbde213cea382a68f1400 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 19 Aug 2026 16:22:05 +0000 Subject: [PATCH 2/6] Fix broken routes/links left by prometheus->pickle replace The literal find-and-replace in the previous commit renamed path segments and identifiers (sidebar doc ids, relative markdown/JSX links, static redirect/header rules) to "pickle" without renaming the underlying files, which are still named/located under "prometheus". Docusaurus is configured with onBrokenLinks: 'throw' and onBrokenMarkdownLinks: 'throw', so these dangling references failed the site build (and, downstream, the Netlify header/redirect rule checks that depend on a successful build). Fixes applied, scoped only to structural identifiers (doc IDs, file paths, route hrefs) - documentation prose keeps the "pickle" wording: - sidebars-calico*.js and all versioned *-sidebars.json: reverted sidebar "id" doc references (e.g. reference/felix/pickle -> reference/felix/prometheus) back to the real, unrenamed doc paths. - 89 relative markdown link targets across current and versioned .mdx docs (e.g. byo-pickle.mdx, ../pickle/index.mdx, felix/pickle.mdx) reverted to the real filenames they point to. - OpenShiftPrometheusOperator.js (6 copies, current + versioned): reverted a route from /operations/monitor/pickle/support to the real /operations/monitor/prometheus/support route. - static/_headers and static/_redirects: reverted fully, since these are infra routing rules tied to the real (unrenamed) page paths. Verified with a repo-wide scan that no markdown link or sidebar doc id still points at a non-existent "pickle" path. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_012uBgAMf3CkcrULiQQMJBTx --- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../configuring/mark-lb-node-for-maintenance.mdx | 2 +- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../kube-controllers/index.mdx | 2 +- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../kube-controllers/index.mdx | 2 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../configuring/mark-lb-node-for-maintenance.mdx | 2 +- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../kube-controllers/index.mdx | 2 +- .../version-22-2-sidebars.json | 14 +++++++------- .../version-23-2-sidebars.json | 14 +++++++------- .../components/OpenShiftPrometheusOperator.js | 2 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../configuring/mark-lb-node-for-maintenance.mdx | 2 +- calico-enterprise/operations/license-options.mdx | 6 +++--- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../monitor/metrics/operator-metrics.mdx | 6 +++--- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../reference/architecture/overview.mdx | 2 +- .../kube-controllers/index.mdx | 2 +- .../components/OpenShiftPrometheusOperator.js | 2 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../operations/monitor/metrics/license-agent.mdx | 2 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../reference/architecture/overview.mdx | 2 +- .../components/OpenShiftPrometheusOperator.js | 2 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../operations/monitor/metrics/license-agent.mdx | 2 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../reference/architecture/overview.mdx | 2 +- .../components/OpenShiftPrometheusOperator.js | 2 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../operations/monitor/metrics/license-agent.mdx | 2 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../reference/architecture/overview.mdx | 2 +- .../components/OpenShiftPrometheusOperator.js | 2 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../configuring/mark-lb-node-for-maintenance.mdx | 2 +- .../operations/license-options.mdx | 6 +++--- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../operations/monitor/metrics/license-agent.mdx | 2 +- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../reference/architecture/overview.mdx | 2 +- .../kube-controllers/index.mdx | 2 +- .../components/OpenShiftPrometheusOperator.js | 2 +- .../multicluster/federation/kubeconfig.mdx | 2 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../configuring/mark-lb-node-for-maintenance.mdx | 2 +- .../operations/license-options.mdx | 6 +++--- .../operations/monitor/metrics/bgp-metrics.mdx | 4 ++-- .../monitor/metrics/operator-metrics.mdx | 6 +++--- .../monitor/metrics/policy-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 2 +- .../operations/monitor/prometheus/support.mdx | 2 +- .../reference/architecture/overview.mdx | 2 +- .../kube-controllers/index.mdx | 2 +- .../version-3.20-2-sidebars.json | 16 ++++++++-------- .../version-3.21-2-sidebars.json | 16 ++++++++-------- .../version-3.22-2-sidebars.json | 16 ++++++++-------- .../version-3.23-2-sidebars.json | 16 ++++++++-------- .../version-3.24-1-sidebars.json | 16 ++++++++-------- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 2 +- .../configuring/add-maglev-load-balancing.mdx | 2 +- .../monitor/monitor-component-metrics.mdx | 2 +- .../version-3.29-sidebars.json | 6 +++--- .../version-3.30-sidebars.json | 6 +++--- .../version-3.31-sidebars.json | 6 +++--- .../version-3.32-sidebars.json | 6 +++--- sidebars-calico-cloud.js | 14 +++++++------- sidebars-calico-enterprise.js | 16 ++++++++-------- sidebars-calico.js | 6 +++--- static/_headers | 4 ++-- static/_redirects | 8 ++++---- 102 files changed, 195 insertions(+), 195 deletions(-) diff --git a/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx b/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx index 3a3a3e6b50..01cd6ccaf3 100644 --- a/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-cloud/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx index 1ec06b87d2..f8a2256055 100644 --- a/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-cloud/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) diff --git a/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx b/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx index 0905c7faec..cea6439523 100644 --- a/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -154,4 +154,4 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-cloud/operations/monitor/metrics/policy-metrics.mdx b/calico-cloud/operations/monitor/metrics/policy-metrics.mdx index 3e094a2aad..fc49d366a1 100644 --- a/calico-cloud/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-cloud/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx index 09329ac659..e567b9b1d2 100644 --- a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-cloud/operations/monitor/prometheus/support.mdx b/calico-cloud/operations/monitor/prometheus/support.mdx index e3dc07855d..1904d83ef2 100644 --- a/calico-cloud/operations/monitor/prometheus/support.mdx +++ b/calico-cloud/operations/monitor/prometheus/support.mdx @@ -16,4 +16,4 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](byo-pickle.mdx) +- [Bring your own Prometheus](byo-prometheus.mdx) diff --git a/calico-cloud/reference/component-resources/kube-controllers/index.mdx b/calico-cloud/reference/component-resources/kube-controllers/index.mdx index bca2123a45..c42646d765 100644 --- a/calico-cloud/reference/component-resources/kube-controllers/index.mdx +++ b/calico-cloud/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx index ca5690981f..e5e6d853d0 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -155,4 +155,4 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx index 3e094a2aad..fc49d366a1 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx index 40bc9364d8..f181f84411 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx index e3dc07855d..1904d83ef2 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx @@ -16,4 +16,4 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](byo-pickle.mdx) +- [Bring your own Prometheus](byo-prometheus.mdx) diff --git a/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx b/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx index bca2123a45..c42646d765 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). diff --git a/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx b/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx index 3a3a3e6b50..01cd6ccaf3 100644 --- a/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-cloud_versioned_docs/version-23-2/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx index 1ec06b87d2..f8a2256055 100644 --- a/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-cloud_versioned_docs/version-23-2/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx index 0905c7faec..cea6439523 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -154,4 +154,4 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx index 3e094a2aad..fc49d366a1 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx index 09329ac659..e567b9b1d2 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx index e3dc07855d..1904d83ef2 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx @@ -16,4 +16,4 @@ $[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](ht If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because $[prodname] creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](byo-pickle.mdx) +- [Bring your own Prometheus](byo-prometheus.mdx) diff --git a/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx b/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx index bca2123a45..c42646d765 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). diff --git a/calico-cloud_versioned_sidebars/version-22-2-sidebars.json b/calico-cloud_versioned_sidebars/version-22-2-sidebars.json index 6a26005220..400169744f 100644 --- a/calico-cloud_versioned_sidebars/version-22-2-sidebars.json +++ b/calico-cloud_versioned_sidebars/version-22-2-sidebars.json @@ -556,14 +556,14 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", + "operations/monitor/prometheus/support", "operations/monitor/metrics/recommended-metrics", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -709,7 +709,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -730,7 +730,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] diff --git a/calico-cloud_versioned_sidebars/version-23-2-sidebars.json b/calico-cloud_versioned_sidebars/version-23-2-sidebars.json index d749c029e9..3c6ab7f058 100644 --- a/calico-cloud_versioned_sidebars/version-23-2-sidebars.json +++ b/calico-cloud_versioned_sidebars/version-23-2-sidebars.json @@ -520,14 +520,14 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", + "operations/monitor/prometheus/support", "operations/monitor/metrics/recommended-metrics", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -670,7 +670,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -691,7 +691,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] diff --git a/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js index 67168b5666..fb017eb782 100644 --- a/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js @@ -18,7 +18,7 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml diff --git a/calico-enterprise/multicluster/federation/kubeconfig.mdx b/calico-enterprise/multicluster/federation/kubeconfig.mdx index 04c12d884c..3f33c16d74 100644 --- a/calico-enterprise/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx b/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx index c3579b10e8..88ff7dd86b 100644 --- a/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx index 2081bb65c8..1bedcc63bd 100644 --- a/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-enterprise/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) diff --git a/calico-enterprise/operations/license-options.mdx b/calico-enterprise/operations/license-options.mdx index 8a5cd015c0..e8148ca588 100644 --- a/calico-enterprise/operations/license-options.mdx +++ b/calico-enterprise/operations/license-options.mdx @@ -81,10 +81,10 @@ The built-in rules include: - **LicenseExpiringWarning**: fires when the license expires in less than 30 days - **LicenseExpiringCritical**: fires when the license expires in less than 7 days, or is invalid -To route these alerts, see [Configure Alertmanager](monitor/pickle/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](monitor/prometheus/alertmanager.mdx). ## Additional resources - [LicenseKey resource](../reference/resources/licensekey.mdx) -- [Configure Alertmanager](monitor/pickle/alertmanager.mdx) -- [Configure Prometheus](monitor/pickle/configure-pickle.mdx) +- [Configure Alertmanager](monitor/prometheus/alertmanager.mdx) +- [Configure Prometheus](monitor/prometheus/configure-prometheus.mdx) diff --git a/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx index 61bf089dc9..01c9ee0e02 100644 --- a/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -164,4 +164,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx b/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx index dc471492dc..89b16ce55b 100644 --- a/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx @@ -124,10 +124,10 @@ The built-in rules include: | `ComponentProgressingWarning` | Component progressing for > 15m | warning | | `ComponentProgressingCritical` | Component progressing for > 30m | critical | -To route these alerts, see [Configure Alertmanager](../pickle/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](../prometheus/alertmanager.mdx). ## Additional resources - [License expiration and renewal](../../license-options.mdx) -- [Configure Prometheus](../pickle/configure-pickle.mdx) -- [BYO Prometheus](../pickle/byo-pickle.mdx) +- [Configure Prometheus](../prometheus/configure-prometheus.mdx) +- [BYO Prometheus](../prometheus/byo-prometheus.mdx) diff --git a/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx index 2a04c6830c..8297fa724a 100644 --- a/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx index f9db9884e8..909c846727 100644 --- a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx @@ -269,7 +269,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-enterprise/operations/monitor/prometheus/support.mdx b/calico-enterprise/operations/monitor/prometheus/support.mdx index 4784b3a6bb..1c7fe337a2 100644 --- a/calico-enterprise/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise/operations/monitor/prometheus/support.mdx @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-pickle.mdx). +For details, see [Bring your own Prometheus](byo-prometheus.mdx). diff --git a/calico-enterprise/reference/architecture/overview.mdx b/calico-enterprise/reference/architecture/overview.mdx index 42fa1566d9..4aca9a3587 100644 --- a/calico-enterprise/reference/architecture/overview.mdx +++ b/calico-enterprise/reference/architecture/overview.mdx @@ -109,7 +109,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise/reference/component-resources/kube-controllers/index.mdx b/calico-enterprise/reference/component-resources/kube-controllers/index.mdx index dad7a2f144..bd9849c941 100644 --- a/calico-enterprise/reference/component-resources/kube-controllers/index.mdx +++ b/calico-enterprise/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js index 67168b5666..fb017eb782 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js @@ -18,7 +18,7 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml diff --git a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx index 98f34519b3..a7f3daaa8d 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/multicluster/federation/kubeconfig.mdx @@ -338,7 +338,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx index 44d219767d..bfca5a474e 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -165,4 +165,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx index 7bc8f8d951..bce3946549 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx @@ -89,4 +89,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../pickle/alertmanager.mdx) +- [Configure Alertmanager](../prometheus/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx index d9d01f1904..9a7afc6f47 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx index c339157ab8..8ccf536b6d 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **Create a service to expose Felix metrics** diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx index cd20ac7b61..70b3566384 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-pickle.mdx). +For details, see [Bring your own Prometheus](byo-prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx index 6e19f0469d..30b5d02f77 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js index 67168b5666..fb017eb782 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js @@ -18,7 +18,7 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml diff --git a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx index 9c1cd02208..f7e99ce537 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx index 44d219767d..bfca5a474e 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -165,4 +165,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx index 45003ae6f2..71afbc6a2f 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx @@ -89,4 +89,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../pickle/alertmanager.mdx) +- [Configure Alertmanager](../prometheus/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx index e331a72722..b0fb0d5fdd 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx index 68cffa4008..f2331ebdc9 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx index cd20ac7b61..70b3566384 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-pickle.mdx). +For details, see [Bring your own Prometheus](byo-prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx index f8dd40946c..da874f5d26 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js index 67168b5666..fb017eb782 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js @@ -18,7 +18,7 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml diff --git a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx index c4a8400af8..c1a6734fe7 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx index ce40f502e0..86b6611000 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -165,4 +165,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources - [Secure $[prodname] Prometheus endpoints](../../comms/secure-metrics.mdx) -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx index 464d65a6a9..c257b61323 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx @@ -89,4 +89,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../pickle/alertmanager.mdx) +- [Configure Alertmanager](../prometheus/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx index 2a04c6830c..8297fa724a 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx index 48e94755c2..3c276c8769 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx index 4784b3a6bb..1c7fe337a2 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-pickle.mdx). +For details, see [Bring your own Prometheus](byo-prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx index 905ddf7e2d..52f6380007 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js index 67168b5666..fb017eb782 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js @@ -18,7 +18,7 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml diff --git a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx index 04c12d884c..3f33c16d74 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx index c3579b10e8..88ff7dd86b 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx index 2081bb65c8..1bedcc63bd 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx index 0b65755575..fe4ff36e86 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/license-options.mdx @@ -61,10 +61,10 @@ The Tigera Operator reports license condition in `tigerastatus`, including a war $[prodname] provides license metrics, such as the number of days until license expiration, through the **License Agent** component and Prometheus. For details on deploying the license agent and creating expiration alerts, see [License metrics](monitor/metrics/license-agent.mdx). -To route license alerts, see [Configure Alertmanager](monitor/pickle/alertmanager.mdx). +To route license alerts, see [Configure Alertmanager](monitor/prometheus/alertmanager.mdx). ## Additional resources - [LicenseKey resource](../reference/resources/licensekey.mdx) -- [Configure Alertmanager](monitor/pickle/alertmanager.mdx) -- [Configure Prometheus](monitor/pickle/configure-pickle.mdx) +- [Configure Alertmanager](monitor/prometheus/alertmanager.mdx) +- [Configure Prometheus](monitor/prometheus/configure-prometheus.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx index 61bf089dc9..01c9ee0e02 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -164,4 +164,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx index f1386fbcef..7b1dbb7379 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx @@ -83,4 +83,4 @@ If the Kubernetes api-server serves on any port other than 6443 or 443, add that ## Additional resources - [LicenseKey resource](../../../reference/resources/licensekey.mdx) -- [Configure Alertmanager](../pickle/alertmanager.mdx) +- [Configure Alertmanager](../prometheus/alertmanager.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx index 2a04c6830c..8297fa724a 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx index 48e94755c2..3c276c8769 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -268,7 +268,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx index 4784b3a6bb..1c7fe337a2 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-pickle.mdx). +For details, see [Bring your own Prometheus](byo-prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx index 064db5744d..413d41a492 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx @@ -144,7 +144,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx index dad7a2f144..bd9849c941 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js index 67168b5666..fb017eb782 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js @@ -18,7 +18,7 @@ export default function OpenShiftPrometheusOperator(props) { Complete this step only if you are using the {prodname} Prometheus operator (including adding your own Prometheus operator). Skip this step if you are using{' '} - BYO Prometheus that you manage yourself. + BYO Prometheus that you manage yourself. {props.operation === 'install' ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml diff --git a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx index 04c12d884c..3f33c16d74 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/multicluster/federation/kubeconfig.mdx @@ -283,7 +283,7 @@ The steps above assume that you are configuring both federated endpoint identity ### Validate federated endpoint identity & multi-cluster networking #### Validate RemoteClusterConfiguration and federated endpoint identity ##### Check remote cluster connection -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](../../reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: ```bash diff --git a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx index c3579b10e8..88ff7dd86b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx index 2081bb65c8..1bedcc63bd 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/networking/configuring/mark-lb-node-for-maintenance.mdx @@ -58,4 +58,4 @@ backends will be excluded at all for that service. ## Additional resources * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Maglev Load Balancing](add-maglev-load-balancing.mdx) -* [Prometheus Metrics](../../reference/component-resources/node/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics](../../reference/component-resources/node/felix/prometheus.mdx#load-balancer-metrics) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx index 8a5cd015c0..e8148ca588 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx @@ -81,10 +81,10 @@ The built-in rules include: - **LicenseExpiringWarning**: fires when the license expires in less than 30 days - **LicenseExpiringCritical**: fires when the license expires in less than 7 days, or is invalid -To route these alerts, see [Configure Alertmanager](monitor/pickle/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](monitor/prometheus/alertmanager.mdx). ## Additional resources - [LicenseKey resource](../reference/resources/licensekey.mdx) -- [Configure Alertmanager](monitor/pickle/alertmanager.mdx) -- [Configure Prometheus](monitor/pickle/configure-pickle.mdx) +- [Configure Alertmanager](monitor/prometheus/alertmanager.mdx) +- [Configure Prometheus](monitor/prometheus/configure-prometheus.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx index 61bf089dc9..01c9ee0e02 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/bgp-metrics.mdx @@ -88,7 +88,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](../pickle/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric @@ -164,4 +164,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources -- [Configuring Prometheus](../pickle/index.mdx) +- [Configuring Prometheus](../prometheus/index.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx index dc471492dc..89b16ce55b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx @@ -124,10 +124,10 @@ The built-in rules include: | `ComponentProgressingWarning` | Component progressing for > 15m | warning | | `ComponentProgressingCritical` | Component progressing for > 30m | critical | -To route these alerts, see [Configure Alertmanager](../pickle/alertmanager.mdx). +To route these alerts, see [Configure Alertmanager](../prometheus/alertmanager.mdx). ## Additional resources - [License expiration and renewal](../../license-options.mdx) -- [Configure Prometheus](../pickle/configure-pickle.mdx) -- [BYO Prometheus](../pickle/byo-pickle.mdx) +- [Configure Prometheus](../prometheus/configure-prometheus.mdx) +- [BYO Prometheus](../prometheus/byo-prometheus.mdx) diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx index 2a04c6830c..8297fa724a 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/policy-metrics.mdx @@ -60,7 +60,7 @@ Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered _stale_, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to -[Configuring Prometheus configuration](../pickle/index.mdx) +[Configuring Prometheus configuration](../prometheus/index.mdx) for more information. Because of metrics being expired, as just described, it is entirely possible diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx index f9db9884e8..909c846727 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx @@ -269,7 +269,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](../../../reference/component-resources/node/felix/configuration.mdx). -For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/pickle.mdx). +For all Prometheus Felix configuration values, see [Felix Prometheus](../../../reference/component-resources/node/felix/prometheus.mdx). **For Windows nodes, create a service to expose Felix metrics** diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx index 4784b3a6bb..1c7fe337a2 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx @@ -28,4 +28,4 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus -For details, see [Bring your own Prometheus](byo-pickle.mdx). +For details, see [Bring your own Prometheus](byo-prometheus.mdx). diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx index 42fa1566d9..4aca9a3587 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx @@ -109,7 +109,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus -**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/pickle.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). +**Main task**: The default monitoring component for collecting $[prodname] policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](../component-resources/node/felix/prometheus.mdx), and [Configure Prometheus](../../operations/monitor/index.mdx). ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx index dad7a2f144..bd9849c941 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/kube-controllers/index.mdx @@ -8,4 +8,4 @@ hide_table_of_contents: true The `$[imageNames.kubeControllers]` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the $[prodname] datastore. - To configure the controllers, see the [KubeControllersConfiguration](../../resources/kubecontrollersconfig.mdx) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](pickle.mdx). +- For exported Prometheus metrics, see [Prometheus statistics](prometheus.mdx). diff --git a/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json index dc26064297..a59ed81a8c 100644 --- a/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.20-2-sidebars.json @@ -704,13 +704,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/support", + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -1004,7 +1004,7 @@ }, "items": [ "reference/component-resources/kube-controllers/configuration", - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -1025,7 +1025,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] @@ -1040,7 +1040,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/pickle" + "reference/component-resources/typha/prometheus" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json index c30c2ccdcd..bb91910248 100644 --- a/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.21-2-sidebars.json @@ -711,13 +711,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/support", + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -1011,7 +1011,7 @@ }, "items": [ "reference/component-resources/kube-controllers/configuration", - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -1032,7 +1032,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] @@ -1047,7 +1047,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/pickle" + "reference/component-resources/typha/prometheus" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json index 650a979e79..799117c106 100644 --- a/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.22-2-sidebars.json @@ -733,13 +733,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/support", + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -1035,7 +1035,7 @@ }, "items": [ "reference/component-resources/kube-controllers/configuration", - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -1056,7 +1056,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] @@ -1071,7 +1071,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/pickle" + "reference/component-resources/typha/prometheus" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json index 07f56c9ebe..7699ec4f01 100644 --- a/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.23-2-sidebars.json @@ -733,13 +733,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/support", + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -1048,7 +1048,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -1069,7 +1069,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] @@ -1084,7 +1084,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/pickle" + "reference/component-resources/typha/prometheus" ] } ] diff --git a/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json b/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json index 8cf6025d44..5ac9289392 100644 --- a/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json +++ b/calico-enterprise_versioned_sidebars/version-3.24-1-sidebars.json @@ -772,13 +772,13 @@ "label": "Prometheus", "link": { "type": "doc", - "id": "operations/monitor/pickle/index" + "id": "operations/monitor/prometheus/index" }, "items": [ - "operations/monitor/pickle/support", - "operations/monitor/pickle/byo-pickle", - "operations/monitor/pickle/configure-pickle", - "operations/monitor/pickle/alertmanager" + "operations/monitor/prometheus/support", + "operations/monitor/prometheus/byo-prometheus", + "operations/monitor/prometheus/configure-prometheus", + "operations/monitor/prometheus/alertmanager" ] }, { @@ -1071,7 +1071,7 @@ "id": "reference/component-resources/kube-controllers/index" }, "items": [ - "reference/component-resources/kube-controllers/pickle" + "reference/component-resources/kube-controllers/prometheus" ] }, { @@ -1092,7 +1092,7 @@ }, "items": [ "reference/component-resources/node/felix/configuration", - "reference/component-resources/node/felix/pickle" + "reference/component-resources/node/felix/prometheus" ] } ] @@ -1107,7 +1107,7 @@ "items": [ "reference/component-resources/typha/overview", "reference/component-resources/typha/configuration", - "reference/component-resources/typha/pickle" + "reference/component-resources/typha/prometheus" ] } ] diff --git a/calico/networking/configuring/add-maglev-load-balancing.mdx b/calico/networking/configuring/add-maglev-load-balancing.mdx index ca3c562212..b6ac582c63 100644 --- a/calico/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico/operations/monitor/monitor-component-metrics.mdx b/calico/operations/monitor/monitor-component-metrics.mdx index 60e93e1edd..c80bfd071d 100644 --- a/calico/operations/monitor/monitor-component-metrics.mdx +++ b/calico/operations/monitor/monitor-component-metrics.mdx @@ -640,7 +640,7 @@ Browse to [http://localhost:9090](http://localhost:9090) you should be able to s :::note -A list of Felix metrics can be [found at this link](../../reference/felix/pickle.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/pickle.mdx) and [Typha](../../reference/typha/pickle.mdx). +A list of Felix metrics can be [found at this link](../../reference/felix/prometheus.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/prometheus.mdx) and [Typha](../../reference/typha/prometheus.mdx). ::: diff --git a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx index b57d87af8e..c0d56726ab 100644 --- a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx @@ -640,7 +640,7 @@ Browse to [http://localhost:9090](http://localhost:9090) you should be able to s :::note -A list of Felix metrics can be [found at this link](../../reference/felix/pickle.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/pickle.mdx) and [Typha](../../reference/typha/pickle.mdx). +A list of Felix metrics can be [found at this link](../../reference/felix/prometheus.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/prometheus.mdx) and [Typha](../../reference/typha/prometheus.mdx). ::: diff --git a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx index b57d87af8e..c0d56726ab 100644 --- a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx @@ -640,7 +640,7 @@ Browse to [http://localhost:9090](http://localhost:9090) you should be able to s :::note -A list of Felix metrics can be [found at this link](../../reference/felix/pickle.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/pickle.mdx) and [Typha](../../reference/typha/pickle.mdx). +A list of Felix metrics can be [found at this link](../../reference/felix/prometheus.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/prometheus.mdx) and [Typha](../../reference/typha/prometheus.mdx). ::: diff --git a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx index b57d87af8e..c0d56726ab 100644 --- a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx @@ -640,7 +640,7 @@ Browse to [http://localhost:9090](http://localhost:9090) you should be able to s :::note -A list of Felix metrics can be [found at this link](../../reference/felix/pickle.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/pickle.mdx) and [Typha](../../reference/typha/pickle.mdx). +A list of Felix metrics can be [found at this link](../../reference/felix/prometheus.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/prometheus.mdx) and [Typha](../../reference/typha/prometheus.mdx). ::: diff --git a/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx b/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx index ca3c562212..b6ac582c63 100644 --- a/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx +++ b/calico_versioned_docs/version-3.32/networking/configuring/add-maglev-load-balancing.mdx @@ -88,7 +88,7 @@ FelixConfiguration should be updated to reflect that: ## Additional resources -* [Prometheus Metrics for Maglev](../../reference/felix/pickle.mdx#load-balancer-metrics) +* [Prometheus Metrics for Maglev](../../reference/felix/prometheus.mdx#load-balancer-metrics) * [FelixConfiguration](../../reference/resources/felixconfig.mdx) * [Enable the eBPF data plane](../../operations/ebpf/enabling-ebpf.mdx) * [Advertise Service IPs with BGP](advertise-service-ips.mdx) diff --git a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx index 60e93e1edd..c80bfd071d 100644 --- a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx @@ -640,7 +640,7 @@ Browse to [http://localhost:9090](http://localhost:9090) you should be able to s :::note -A list of Felix metrics can be [found at this link](../../reference/felix/pickle.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/pickle.mdx) and [Typha](../../reference/typha/pickle.mdx). +A list of Felix metrics can be [found at this link](../../reference/felix/prometheus.mdx). Similar lists can be found for [kube-controllers](../../reference/kube-controllers/prometheus.mdx) and [Typha](../../reference/typha/prometheus.mdx). ::: diff --git a/calico_versioned_sidebars/version-3.29-sidebars.json b/calico_versioned_sidebars/version-3.29-sidebars.json index c51f41d804..ce9ee97984 100644 --- a/calico_versioned_sidebars/version-3.29-sidebars.json +++ b/calico_versioned_sidebars/version-3.29-sidebars.json @@ -664,7 +664,7 @@ "type": "doc", "id": "reference/felix/index" }, - "items": ["reference/felix/configuration", "reference/felix/pickle"] + "items": ["reference/felix/configuration", "reference/felix/prometheus"] }, { "type": "category", @@ -673,7 +673,7 @@ "type": "doc", "id": "reference/typha/index" }, - "items": ["reference/typha/overview", "reference/typha/configuration", "reference/typha/pickle"] + "items": ["reference/typha/overview", "reference/typha/configuration", "reference/typha/prometheus"] }, "reference/configure-cni-plugins", { @@ -683,7 +683,7 @@ "type": "doc", "id": "reference/kube-controllers/index" }, - "items": ["reference/kube-controllers/configuration", "reference/kube-controllers/pickle"] + "items": ["reference/kube-controllers/configuration", "reference/kube-controllers/prometheus"] }, { "type": "category", diff --git a/calico_versioned_sidebars/version-3.30-sidebars.json b/calico_versioned_sidebars/version-3.30-sidebars.json index 230e22e86b..bcba7319c3 100644 --- a/calico_versioned_sidebars/version-3.30-sidebars.json +++ b/calico_versioned_sidebars/version-3.30-sidebars.json @@ -713,7 +713,7 @@ }, "items": [ "reference/felix/configuration", - "reference/felix/pickle" + "reference/felix/prometheus" ] }, { @@ -726,7 +726,7 @@ "items": [ "reference/typha/overview", "reference/typha/configuration", - "reference/typha/pickle" + "reference/typha/prometheus" ] }, "reference/configure-cni-plugins", @@ -739,7 +739,7 @@ }, "items": [ "reference/kube-controllers/configuration", - "reference/kube-controllers/pickle" + "reference/kube-controllers/prometheus" ] }, { diff --git a/calico_versioned_sidebars/version-3.31-sidebars.json b/calico_versioned_sidebars/version-3.31-sidebars.json index 08f4ac7709..d3488f0177 100644 --- a/calico_versioned_sidebars/version-3.31-sidebars.json +++ b/calico_versioned_sidebars/version-3.31-sidebars.json @@ -726,7 +726,7 @@ }, "items": [ "reference/felix/configuration", - "reference/felix/pickle" + "reference/felix/prometheus" ] }, { @@ -739,7 +739,7 @@ "items": [ "reference/typha/overview", "reference/typha/configuration", - "reference/typha/pickle" + "reference/typha/prometheus" ] }, "reference/configure-cni-plugins", @@ -752,7 +752,7 @@ }, "items": [ "reference/kube-controllers/configuration", - "reference/kube-controllers/pickle" + "reference/kube-controllers/prometheus" ] }, { diff --git a/calico_versioned_sidebars/version-3.32-sidebars.json b/calico_versioned_sidebars/version-3.32-sidebars.json index f28ddbae52..600f89341a 100644 --- a/calico_versioned_sidebars/version-3.32-sidebars.json +++ b/calico_versioned_sidebars/version-3.32-sidebars.json @@ -750,7 +750,7 @@ }, "items": [ "reference/felix/configuration", - "reference/felix/pickle" + "reference/felix/prometheus" ] }, { @@ -763,7 +763,7 @@ "items": [ "reference/typha/overview", "reference/typha/configuration", - "reference/typha/pickle" + "reference/typha/prometheus" ] }, "reference/configure-cni-plugins", @@ -776,7 +776,7 @@ }, "items": [ "reference/kube-controllers/configuration", - "reference/kube-controllers/pickle" + "reference/kube-controllers/prometheus" ] }, { diff --git a/sidebars-calico-cloud.js b/sidebars-calico-cloud.js index c84e0ef24a..514605887b 100644 --- a/sidebars-calico-cloud.js +++ b/sidebars-calico-cloud.js @@ -406,13 +406,13 @@ module.exports = { { type: 'category', label: 'Prometheus', - link: { type: 'doc', id: 'operations/monitor/pickle/index' }, + link: { type: 'doc', id: 'operations/monitor/prometheus/index' }, items: [ - 'operations/monitor/pickle/support', + 'operations/monitor/prometheus/support', 'operations/monitor/metrics/recommended-metrics', - 'operations/monitor/pickle/byo-pickle', - 'operations/monitor/pickle/configure-pickle', - 'operations/monitor/pickle/alertmanager', + 'operations/monitor/prometheus/byo-prometheus', + 'operations/monitor/prometheus/configure-prometheus', + 'operations/monitor/prometheus/alertmanager', ], }, { @@ -528,7 +528,7 @@ module.exports = { label: 'Calico Cloud Kubernetes controllers', link: { type: 'doc', id: 'reference/component-resources/kube-controllers/index' }, items: [ - 'reference/component-resources/kube-controllers/pickle', + 'reference/component-resources/kube-controllers/prometheus', ], }, { @@ -543,7 +543,7 @@ module.exports = { link: { type: 'doc', id: 'reference/component-resources/node/felix/index' }, items: [ 'reference/component-resources/node/felix/configuration', - 'reference/component-resources/node/felix/pickle', + 'reference/component-resources/node/felix/prometheus', ], }, ], diff --git a/sidebars-calico-enterprise.js b/sidebars-calico-enterprise.js index 5fb294f9d1..0f9bf82a0a 100644 --- a/sidebars-calico-enterprise.js +++ b/sidebars-calico-enterprise.js @@ -595,12 +595,12 @@ module.exports = { { type: 'category', label: 'Prometheus', - link: { type: 'doc', id: 'operations/monitor/pickle/index' }, + link: { type: 'doc', id: 'operations/monitor/prometheus/index' }, items: [ - 'operations/monitor/pickle/support', - 'operations/monitor/pickle/byo-pickle', - 'operations/monitor/pickle/configure-pickle', - 'operations/monitor/pickle/alertmanager', + 'operations/monitor/prometheus/support', + 'operations/monitor/prometheus/byo-prometheus', + 'operations/monitor/prometheus/configure-prometheus', + 'operations/monitor/prometheus/alertmanager', ], }, { @@ -828,7 +828,7 @@ module.exports = { label: 'Calico Enterprise Kubernetes controllers', link: { type: 'doc', id: 'reference/component-resources/kube-controllers/index' }, items: [ - 'reference/component-resources/kube-controllers/pickle', + 'reference/component-resources/kube-controllers/prometheus', ], }, { @@ -843,7 +843,7 @@ module.exports = { link: { type: 'doc', id: 'reference/component-resources/node/felix/index' }, items: [ 'reference/component-resources/node/felix/configuration', - 'reference/component-resources/node/felix/pickle', + 'reference/component-resources/node/felix/prometheus', ], }, ], @@ -855,7 +855,7 @@ module.exports = { items: [ 'reference/component-resources/typha/overview', 'reference/component-resources/typha/configuration', - 'reference/component-resources/typha/pickle', + 'reference/component-resources/typha/prometheus', ], }, ], diff --git a/sidebars-calico.js b/sidebars-calico.js index f3192a778d..474097260d 100644 --- a/sidebars-calico.js +++ b/sidebars-calico.js @@ -758,7 +758,7 @@ module.exports = { }, items: [ 'reference/felix/configuration', - 'reference/felix/pickle', + 'reference/felix/prometheus', ], }, { @@ -771,7 +771,7 @@ module.exports = { items: [ 'reference/typha/overview', 'reference/typha/configuration', - 'reference/typha/pickle', + 'reference/typha/prometheus', ], }, 'reference/configure-cni-plugins', @@ -784,7 +784,7 @@ module.exports = { }, items: [ 'reference/kube-controllers/configuration', - 'reference/kube-controllers/pickle', + 'reference/kube-controllers/prometheus', ], }, { diff --git a/static/_headers b/static/_headers index dc01231c9c..85e004308a 100644 --- a/static/_headers +++ b/static/_headers @@ -222,7 +222,7 @@ X-Robots-Tag: noindex /calico-enterprise/latest/operations/monitor X-Robots-Tag: noindex -/calico-enterprise/latest/operations/monitor/pickle +/calico-enterprise/latest/operations/monitor/prometheus X-Robots-Tag: noindex /calico-enterprise/latest/operations/troubleshoot X-Robots-Tag: noindex @@ -384,7 +384,7 @@ X-Robots-Tag: noindex /calico-cloud/operations/monitor X-Robots-Tag: noindex -/calico-cloud/operations/monitor/pickle +/calico-cloud/operations/monitor/prometheus X-Robots-Tag: noindex /calico-cloud/operations X-Robots-Tag: noindex diff --git a/static/_redirects b/static/_redirects index 8b09e94e06..f8618d2960 100644 --- a/static/_redirects +++ b/static/_redirects @@ -250,8 +250,8 @@ /maintenance/kubernetes-upgrade-tsee/operator https://docs.tigera.io/calico-enterprise/latest/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator 301 /maintenance/manifest-archive https://docs.tigera.io/calico-enterprise/latest/getting-started/manifest-archive 301 /maintenance/monitor/metrics/metrics https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/ 301 -/maintenance/monitor/pickle/pickle https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/ 301 -/maintenance/monitor/support https://docs.tigera.io/calico-enterprise/latest/monitor/pickle/support 301 +/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/ 301 +/maintenance/monitor/support https://docs.tigera.io/calico-enterprise/latest/monitor/prometheus/support 301 /maintenance/monitor/elasticsearch-and-fluentd-metrics /calico-enterprise/latest/operations/monitor/metrics/elasticsearch-and-fluentd-metrics 301 /maintenance/monitor/license-agent /calico-enterprise/latest/operations/license-options 301 /maintenance/openshift-upgrade https://docs.tigera.io/calico-enterprise/latest/getting-started/upgrading/upgrading-enterprise/openshift-upgrade 301 @@ -292,12 +292,12 @@ /reference/compliance-reports/* https://docs.tigera.io/calico-enterprise/latest/compliance 301 /reference/felix/ https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/ 301 /reference/felix/configuration https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration 301 -/reference/felix/pickle https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle 301 +/reference/felix/prometheus https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus 301 /reference/host-endpoints/donottrack https://docs.tigera.io/calico-enterprise/latest/reference/host-endpoints 301 /reference/host-endpoints/tutorial https://docs.tigera.io/calico-enterprise/latest/reference/host-endpoints 301 /reference/kube-controllers/ https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/ 301 /reference/kube-controllers/configuration https://docs.tigera.io/calico-enterprise/latest/reference/resources/kubecontrollersconfig 301 -/reference/kube-controllers/pickle https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/pickle 301 +/reference/kube-controllers/prometheus https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/prometheus 301 /reference/legal/ https://docs.tigera.io/calico-enterprise/latest/reference/attribution 301 /reference/node/ https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/ 301 /reference/node/configuration https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/configuration 301 From 2a27b8821791ebca4bfef128ed1efe39820273e9 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 19 Aug 2026 16:37:07 +0000 Subject: [PATCH 3/6] Fix broken DocCardLink docId references left by prometheus->pickle replace The blind prometheus->pickle string replace touched docId='...' values inside components in several reference/operations index pages, even though the underlying doc files/directories (e.g. reference/felix/prometheus.mdx, operations/monitor/prometheus/support.mdx) were never renamed. This produced doc ids like "reference/felix/pickle" and "operations/monitor/pickle/support" that point at nonexistent docs, which docusaurus build fails hard on during static-file rendering (both the default and BUILD_NEXT=true Netlify build targets). Reproduced locally with yarn 4.9.2 (via @yarnpkg/cli-dist, since corepack's fetch to repo.yarnpkg.com was blocked by the proxy) and confirmed both `yarn build` and `BUILD_NEXT=true yarn build` complete successfully after restoring the "prometheus" path segment in the affected docId values. --- calico-cloud/operations/index.mdx | 8 ++++---- calico-cloud/reference/index.mdx | 4 ++-- .../version-22-2/operations/index.mdx | 8 ++++---- .../version-22-2/reference/index.mdx | 4 ++-- .../version-23-2/operations/index.mdx | 8 ++++---- .../version-23-2/reference/index.mdx | 4 ++-- calico-enterprise/operations/index.mdx | 8 ++++---- .../version-3.20-2/operations/index.mdx | 8 ++++---- .../version-3.21-2/operations/index.mdx | 8 ++++---- .../version-3.22-2/operations/index.mdx | 8 ++++---- .../version-3.23-2/operations/index.mdx | 8 ++++---- .../version-3.24-1/operations/index.mdx | 8 ++++---- calico/reference/index.mdx | 4 ++-- calico_versioned_docs/version-3.29/reference/index.mdx | 4 ++-- calico_versioned_docs/version-3.30/reference/index.mdx | 4 ++-- calico_versioned_docs/version-3.31/reference/index.mdx | 4 ++-- calico_versioned_docs/version-3.32/reference/index.mdx | 4 ++-- 17 files changed, 52 insertions(+), 52 deletions(-) diff --git a/calico-cloud/operations/index.mdx b/calico-cloud/operations/index.mdx index 3e97c60090..f8da8da396 100644 --- a/calico-cloud/operations/index.mdx +++ b/calico-cloud/operations/index.mdx @@ -18,11 +18,11 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring - + - - - + + + diff --git a/calico-cloud/reference/index.mdx b/calico-cloud/reference/index.mdx index 5f6d4e9f72..96baeba785 100644 --- a/calico-cloud/reference/index.mdx +++ b/calico-cloud/reference/index.mdx @@ -65,10 +65,10 @@ APIs, CLI, architecture and design, and FAQ. - + - + ## Configuration on public clouds diff --git a/calico-cloud_versioned_docs/version-22-2/operations/index.mdx b/calico-cloud_versioned_docs/version-22-2/operations/index.mdx index 8afca631fe..bd493f19ba 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/index.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/index.mdx @@ -25,11 +25,11 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring - + - - - + + + diff --git a/calico-cloud_versioned_docs/version-22-2/reference/index.mdx b/calico-cloud_versioned_docs/version-22-2/reference/index.mdx index 466c054ca6..973c1bc0ce 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/index.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/index.mdx @@ -68,10 +68,10 @@ APIs, CLI, architecture and design, and FAQ. - + - + ## Configuration on public clouds diff --git a/calico-cloud_versioned_docs/version-23-2/operations/index.mdx b/calico-cloud_versioned_docs/version-23-2/operations/index.mdx index 3e97c60090..f8da8da396 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/index.mdx @@ -18,11 +18,11 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring - + - - - + + + diff --git a/calico-cloud_versioned_docs/version-23-2/reference/index.mdx b/calico-cloud_versioned_docs/version-23-2/reference/index.mdx index 5f6d4e9f72..96baeba785 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/index.mdx @@ -65,10 +65,10 @@ APIs, CLI, architecture and design, and FAQ. - + - + ## Configuration on public clouds diff --git a/calico-enterprise/operations/index.mdx b/calico-enterprise/operations/index.mdx index 222f8dbce8..50185d43f2 100644 --- a/calico-enterprise/operations/index.mdx +++ b/calico-enterprise/operations/index.mdx @@ -46,10 +46,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx index 7053f79df6..adcc11f46d 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx @@ -56,10 +56,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx index 7053f79df6..adcc11f46d 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/index.mdx @@ -56,10 +56,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx index 606ba91828..1c52760c9c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/index.mdx @@ -56,10 +56,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx index a9e1b147e7..87d695c066 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/index.mdx @@ -44,10 +44,10 @@ See [Provide TLS certificates for $[prodname] components](./comms/index.mdx) for ## Monitoring - - - - + + + + diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx index 222f8dbce8..50185d43f2 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/index.mdx @@ -46,10 +46,10 @@ Post-installation tasks for managing Calico Enterprise. ## Monitoring - - - - + + + + diff --git a/calico/reference/index.mdx b/calico/reference/index.mdx index bd5dfd7aa4..3d8bdd9c66 100644 --- a/calico/reference/index.mdx +++ b/calico/reference/index.mdx @@ -84,14 +84,14 @@ APIs, CLI, architecture and design, and FAQ. ## Felix - + ## Typha - + diff --git a/calico_versioned_docs/version-3.29/reference/index.mdx b/calico_versioned_docs/version-3.29/reference/index.mdx index 4d19b13dd6..908ec50c5f 100644 --- a/calico_versioned_docs/version-3.29/reference/index.mdx +++ b/calico_versioned_docs/version-3.29/reference/index.mdx @@ -83,14 +83,14 @@ APIs, CLI, architecture and design, and FAQ. ## Felix - + ## Typha - + diff --git a/calico_versioned_docs/version-3.30/reference/index.mdx b/calico_versioned_docs/version-3.30/reference/index.mdx index 5e3ae24435..7ee1e66105 100644 --- a/calico_versioned_docs/version-3.30/reference/index.mdx +++ b/calico_versioned_docs/version-3.30/reference/index.mdx @@ -85,14 +85,14 @@ APIs, CLI, architecture and design, and FAQ. ## Felix - + ## Typha - + diff --git a/calico_versioned_docs/version-3.31/reference/index.mdx b/calico_versioned_docs/version-3.31/reference/index.mdx index 5e3ae24435..7ee1e66105 100644 --- a/calico_versioned_docs/version-3.31/reference/index.mdx +++ b/calico_versioned_docs/version-3.31/reference/index.mdx @@ -85,14 +85,14 @@ APIs, CLI, architecture and design, and FAQ. ## Felix - + ## Typha - + diff --git a/calico_versioned_docs/version-3.32/reference/index.mdx b/calico_versioned_docs/version-3.32/reference/index.mdx index bd5dfd7aa4..3d8bdd9c66 100644 --- a/calico_versioned_docs/version-3.32/reference/index.mdx +++ b/calico_versioned_docs/version-3.32/reference/index.mdx @@ -84,14 +84,14 @@ APIs, CLI, architecture and design, and FAQ. ## Felix - + ## Typha - + From 8c981b765fcb6e52af4d41e7e3f4826f7c7e32ec Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 19 Aug 2026 17:00:47 +0000 Subject: [PATCH 4/6] Revert real external prometheus.io/prom identifiers broken by blind rename The prometheus->pickle sed also touched real external URLs and identifiers that must resolve on the live internet: prometheus.io doc links, the prom/prometheus Docker Hub image name, the github.com/prometheus/client_golang attribution entry, and the matching skip-list/comment entries in the crawler link-check test. Revert just those occurrences back to "prometheus" while leaving all narrative/prose and internally-defined identifiers (e.g. the pickle-dashboard-svc example service name) as "pickle". --- __tests__/crawler.test.js | 6 +++--- calico-cloud/operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- calico-cloud/operations/monitor/prometheus/support.mdx | 2 +- calico-cloud/reference/attribution.mdx | 4 ++-- calico-cloud/reference/installation/_api.mdx | 2 +- calico-cloud/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../version-22-2/operations/monitor/prometheus/support.mdx | 2 +- .../version-22-2/reference/attribution.mdx | 4 ++-- .../version-22-2/reference/installation/_api.mdx | 2 +- .../version-22-2/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../version-23-2/operations/monitor/prometheus/support.mdx | 2 +- .../version-23-2/reference/attribution.mdx | 4 ++-- .../version-23-2/reference/installation/_api.mdx | 2 +- .../version-23-2/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- calico-enterprise/operations/monitor/prometheus/support.mdx | 2 +- calico-enterprise/reference/installation/_api.mdx | 2 +- calico-enterprise/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../operations/monitor/prometheus/support.mdx | 2 +- .../version-3.20-2/reference/installation/_api.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../operations/monitor/prometheus/support.mdx | 2 +- .../version-3.21-2/reference/installation/_api.mdx | 2 +- .../version-3.21-2/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../operations/monitor/prometheus/support.mdx | 2 +- .../version-3.22-2/reference/installation/_api.mdx | 2 +- .../version-3.22-2/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../operations/monitor/prometheus/support.mdx | 2 +- .../version-3.23-2/reference/installation/_api.mdx | 2 +- .../version-3.23-2/threat/configuring-webhooks.mdx | 2 +- .../operations/monitor/prometheus/alertmanager.mdx | 6 +++--- .../operations/monitor/prometheus/configure-prometheus.mdx | 4 ++-- .../operations/monitor/prometheus/support.mdx | 2 +- .../version-3.24-1/reference/installation/_api.mdx | 2 +- .../version-3.24-1/threat/configuring-webhooks.mdx | 2 +- calico/operations/monitor/monitor-component-metrics.mdx | 4 ++-- .../operations/monitor/monitor-component-metrics.mdx | 4 ++-- .../operations/monitor/monitor-component-metrics.mdx | 4 ++-- .../operations/monitor/monitor-component-metrics.mdx | 4 ++-- .../operations/monitor/monitor-component-metrics.mdx | 4 ++-- 53 files changed, 90 insertions(+), 90 deletions(-) diff --git a/__tests__/crawler.test.js b/__tests__/crawler.test.js index 916daac095..8f59cc2d4b 100644 --- a/__tests__/crawler.test.js +++ b/__tests__/crawler.test.js @@ -135,7 +135,7 @@ test('Crawl the docs and execute tests', async () => { 'https://tools.ietf.org/html/rfc1123', 'http://cr.yp.to/libtai/tai64.html#tai64n', 'https://thenewstack.io/faster-troubleshooting-with-dynamic-packet-capture/', //==>Origin: http://localhost:4242/calico-cloud/visibility/packetcapture - 'https://golang.org/pkg/crypto/tls/#ClientAuthType', //==>Origin: https://downloads.tigera.io/ee/v3.17.0/manifests/tigera-pickle-operator.yaml. The dead link is automatically redirected to a working page, so no fix needed in the origin. + 'https://golang.org/pkg/crypto/tls/#ClientAuthType', //==>Origin: https://downloads.tigera.io/ee/v3.17.0/manifests/tigera-prometheus-operator.yaml. The dead link is automatically redirected to a working page, so no fix needed in the origin. 'https://downloads.tigera.io/ee/archives/release-master-master.tgz', //==> This started after redesigning the archive procedure. 'http://nginx-svc.curl-ns.svc.cluster.local:80', 'http://nginx-svc.service-ns.svc.cluster.local:80', @@ -188,8 +188,8 @@ test('Crawl the docs and execute tests', async () => { 'https://www.tigera.io/blog/why-bgp/', 'https://docs.nginx.com/nginx-ingress-controller/configuration/', 'https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource', - 'https://pickle.io/docs/pickle/latest/disabled_features/', // ==>Origin: https://downloads.tigera.io/ee/v3.17.4/manifests/tigera-pickle-operator.yaml - 'https://pickle.io/docs/pickle/latest/feature_flags/', // ==>Origin: https://downloads.tigera.io/ee/v3.20.0-1.0/manifests/tigera-pickle-operator.yaml + 'https://prometheus.io/docs/prometheus/latest/disabled_features/', // ==>Origin: https://downloads.tigera.io/ee/v3.17.4/manifests/tigera-prometheus-operator.yaml + 'https://prometheus.io/docs/prometheus/latest/feature_flags/', // ==>Origin: https://downloads.tigera.io/ee/v3.20.0-1.0/manifests/tigera-prometheus-operator.yaml 'https://docs.fluentd.org/filter/grep', 'https://techcommunity.microsoft.com/t5/networking-blog/direct-server-return-dsr-in-a-nutshell/ba-p/693710', 'https://www.f5.com/glossary/cookie-poisoning', //TEMPORARY diff --git a/calico-cloud/operations/monitor/prometheus/alertmanager.mdx b/calico-cloud/operations/monitor/prometheus/alertmanager.mdx index e94fa0f143..0bacf242c4 100644 --- a/calico-cloud/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-cloud/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Cloud connected cluster to route Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx index a91ef9ac47..e0016226c3 100644 --- a/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-cloud/operations/monitor/prometheus/support.mdx b/calico-cloud/operations/monitor/prometheus/support.mdx index 1904d83ef2..c284d79469 100644 --- a/calico-cloud/operations/monitor/prometheus/support.mdx +++ b/calico-cloud/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Cloud connected clusters ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-cloud/reference/attribution.mdx b/calico-cloud/reference/attribution.mdx index 511c58de91..c66b171c27 100644 --- a/calico-cloud/reference/attribution.mdx +++ b/calico-cloud/reference/attribution.mdx @@ -1426,8 +1426,8 @@ In the table below, you can look at the details of each project and license asso Tigera Proprietary - github.com/pickle/client_golang/ - github.com/pickle/client_golang/pickle-v1.7.1 + github.com/prometheus/client_golang/ + github.com/prometheus/client_golang/prometheus-v1.7.1 Apache 2.0 diff --git a/calico-cloud/reference/installation/_api.mdx b/calico-cloud/reference/installation/_api.mdx index 03f65ba63e..5b6d944a67 100644 --- a/calico-cloud/reference/installation/_api.mdx +++ b/calico-cloud/reference/installation/_api.mdx @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-cloud/threat/configuring-webhooks.mdx b/calico-cloud/threat/configuring-webhooks.mdx index 4a55693b8a..3f0cf16d61 100644 --- a/calico-cloud/threat/configuring-webhooks.mdx +++ b/calico-cloud/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx index e94fa0f143..0bacf242c4 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Cloud connected cluster to route Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx index 8caca4c51c..842742a6ea 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx index 1904d83ef2..c284d79469 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Cloud connected clusters ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx b/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx index 511c58de91..c66b171c27 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/attribution.mdx @@ -1426,8 +1426,8 @@ In the table below, you can look at the details of each project and license asso Tigera Proprietary - github.com/pickle/client_golang/ - github.com/pickle/client_golang/pickle-v1.7.1 + github.com/prometheus/client_golang/ + github.com/prometheus/client_golang/prometheus-v1.7.1 Apache 2.0 diff --git a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx index 57f97bab95..21483f65a4 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx b/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx index 4a55693b8a..3f0cf16d61 100644 --- a/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx +++ b/calico-cloud_versioned_docs/version-22-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx index e94fa0f143..0bacf242c4 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Cloud connected cluster to route Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx index a91ef9ac47..e0016226c3 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx index 1904d83ef2..c284d79469 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Cloud connected clusters ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx b/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx index 511c58de91..c66b171c27 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/attribution.mdx @@ -1426,8 +1426,8 @@ In the table below, you can look at the details of each project and license asso Tigera Proprietary - github.com/pickle/client_golang/ - github.com/pickle/client_golang/pickle-v1.7.1 + github.com/prometheus/client_golang/ + github.com/prometheus/client_golang/prometheus-v1.7.1 Apache 2.0 diff --git a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx index 03f65ba63e..5b6d944a67 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx b/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx index 4a55693b8a..3f0cf16d61 100644 --- a/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx +++ b/calico-cloud_versioned_docs/version-23-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx index 1534f898a9..7002f1fd19 100644 --- a/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx index ba84d577af..adad191920 100644 --- a/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-enterprise/operations/monitor/prometheus/support.mdx b/calico-enterprise/operations/monitor/prometheus/support.mdx index 1c7fe337a2..0274070894 100644 --- a/calico-enterprise/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index 3207e1c9a8..7a7051abee 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -2188,7 +2188,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise/threat/configuring-webhooks.mdx b/calico-enterprise/threat/configuring-webhooks.mdx index b5d76bb09b..01b05b33ca 100644 --- a/calico-enterprise/threat/configuring-webhooks.mdx +++ b/calico-enterprise/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx index dcd8f3a73c..65cb40ca08 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager, a Prometheus feature that routes alerts. Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx index 3f97261b95..e805423e3c 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx index 70b3566384..8461bf44ef 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Prometheus support in Calico Enterprise. ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx index bda7643bff..a841978c30 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx @@ -2408,7 +2408,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx index dcd8f3a73c..65cb40ca08 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager, a Prometheus feature that routes alerts. Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx index 3f97261b95..e805423e3c 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx index 70b3566384..8461bf44ef 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Prometheus support in Calico Enterprise. ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx index e45aff6298..4bcc7309af 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx @@ -2476,7 +2476,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx index e01b41ea7c..0754a384c1 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx index 1534f898a9..7002f1fd19 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx index f436e2fb9c..a3471e9857 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx index 1c7fe337a2..0274070894 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx index cdeb35b55f..6bf96da4d3 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx @@ -2513,7 +2513,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx index b5d76bb09b..01b05b33ca 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx index 1534f898a9..7002f1fd19 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx index ba84d577af..adad191920 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx index 1c7fe337a2..0274070894 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx index 3ede2822ef..c4dd15887e 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx @@ -2514,7 +2514,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx index b5d76bb09b..01b05b33ca 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx index 1534f898a9..7002f1fd19 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/alertmanager.mdx @@ -7,7 +7,7 @@ description: Configure Alertmanager in a Calico Enterprise cluster to route Prom Alertmanager is used by $[prodname] to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config @@ -47,7 +47,7 @@ container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). For more advice on writing alertmanager configuration files, see the -[alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +[alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules @@ -99,5 +99,5 @@ receivers: ``` More information, including descriptions of the various options can be found under the -[route section](https://pickle.io/docs/alerting/latest/configuration/#route) +[route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx index ba84d577af..adad191920 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx @@ -77,8 +77,8 @@ spec: ## Creating a new alerting rule Creating a new alerting rule is straightforward once you figure out what you -want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) -and [Queries](https://pickle.io/docs/querying/examples/) for more +want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) +and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx index 1c7fe337a2..0274070894 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/support.mdx @@ -6,7 +6,7 @@ description: Reference for Prometheus support in Calico Enterprise covering the ## Big picture -$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +$[prodname] uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from $[prodname] components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx index 803fe9b05d..7957e821fe 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx @@ -2204,7 +2204,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx b/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx index b5d76bb09b..01b05b33ca 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/threat/configuring-webhooks.mdx @@ -31,7 +31,7 @@ Your target application must be configured to receive data from the $[prodname] If no namespace is specified in the Alertmanager service resource, then this value is `default`. Alertmanager integration in $[prodname] leverages the API v2 exposed by the Alertmanager. - For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). * **Generic JSON.** You must have a webhook URL for any other application you want the $[prodname] webhook to send alerts to. ## Create a webhook for security event alerts diff --git a/calico/operations/monitor/monitor-component-metrics.mdx b/calico/operations/monitor/monitor-component-metrics.mdx index c80bfd071d..e5c5cd67fe 100644 --- a/calico/operations/monitor/monitor-component-metrics.mdx +++ b/calico/operations/monitor/monitor-component-metrics.mdx @@ -439,7 +439,7 @@ We can configure Prometheus using a ConfigMap to persistently store the desired :::note -A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). +A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). ::: @@ -597,7 +597,7 @@ spec: serviceAccountName: calico-pickle-user containers: - name: pickle-pod - image: prom/pickle + image: prom/prometheus resources: limits: memory: "128Mi" diff --git a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx index c0d56726ab..15ebf6bcd3 100644 --- a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx @@ -439,7 +439,7 @@ We can configure Prometheus using a ConfigMap to persistently store the desired :::note -A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). +A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). ::: @@ -597,7 +597,7 @@ spec: serviceAccountName: calico-pickle-user containers: - name: pickle-pod - image: prom/pickle + image: prom/prometheus resources: limits: memory: "128Mi" diff --git a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx index c0d56726ab..15ebf6bcd3 100644 --- a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx @@ -439,7 +439,7 @@ We can configure Prometheus using a ConfigMap to persistently store the desired :::note -A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). +A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). ::: @@ -597,7 +597,7 @@ spec: serviceAccountName: calico-pickle-user containers: - name: pickle-pod - image: prom/pickle + image: prom/prometheus resources: limits: memory: "128Mi" diff --git a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx index c0d56726ab..15ebf6bcd3 100644 --- a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx @@ -439,7 +439,7 @@ We can configure Prometheus using a ConfigMap to persistently store the desired :::note -A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). +A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). ::: @@ -597,7 +597,7 @@ spec: serviceAccountName: calico-pickle-user containers: - name: pickle-pod - image: prom/pickle + image: prom/prometheus resources: limits: memory: "128Mi" diff --git a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx index c80bfd071d..e5c5cd67fe 100644 --- a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx +++ b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx @@ -439,7 +439,7 @@ We can configure Prometheus using a ConfigMap to persistently store the desired :::note -A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). +A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). ::: @@ -597,7 +597,7 @@ spec: serviceAccountName: calico-pickle-user containers: - name: pickle-pod - image: prom/pickle + image: prom/prometheus resources: limits: memory: "128Mi" From 7920bc9449e94352c011e5a73ddaa4623ed50478 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 19 Aug 2026 17:24:52 +0000 Subject: [PATCH 5/6] Revert more real external identifiers broken by prometheus->pickle rename Round 3 of link-checker fixes on this branch. The blind sed also corrupted several categories of real external/absolute identifiers that the previous two rounds missed: - Third-party license attribution pages (static/calico//licenses/*.html, static/calico/3.26/licenses/index.html): every github.com/prometheus/*, github.com/grpc-ecosystem/go-grpc-prometheus, github.com/prometheus-operator/ prometheus-operator, proxy.golang.org/.../prometheus/*, prometheus.io mailto addresses, and "The Prometheus Authors" copyright lines - all real upstream Go dependency records. - {filesUrl}/manifests/tigera-prometheus-operator.yaml, .../prometheus-operator-crds.yaml and .../manifests/prometheus/*-service-monitor.yaml references (calico-enterprise and calico-cloud install/upgrade/monitoring docs, current + all versioned copies). filesUrl resolves to the real downloads.tigera.io manifest host, so these were literal dead links caught by the crawler's file-extension URL regex. - __tests__/data/urls_with_canonicals.txt and urls_projectcalico.docs.tigera.io.txt: fixture lists of real historical docs.tigera.io URLs used by the redirect/canonical tests - restored the frozen legacy page slugs (felix/prometheus, kube-controllers/ prometheus, maintenance/monitor/prometheus, etc.) that will never be renamed. - static/{calico,calico-enterprise,calico-cloud}/llms{,-full}.txt: these are committed build artifacts (only regenerated by `make generate-llms`, not by the normal `make netlify` build), so they still shipped the original broken github.com/prometheus/*, prometheus.io, downloads.tigera.io manifest paths, and absolute docs.tigera.io/.../reference/felix/prometheus-style links (the actual page files were never renamed, only prose, so the real slug is still "prometheus"). Reverted the same categories as above within these mirrors. - __tmp_prometheus_job_name: a real Prometheus Operator relabeling label named verbatim in the CRD API reference (_api.mdx) and its stale llms-full.txt mirror. Left untouched: internally-renamed identifiers that are self-consistent across the docs (tigera-prometheus-operator -> tigera-pickle-operator equivalents used as local/example filenames, calico-node-pickle service/secret names, the tigera-pickle namespace, the pickle-dashboard-svc example already in the crawler skip list, and product image names like tigera/pickle-operator in releases.json). Verified via the crawler's own link-extraction regex (https?://[-a-zA-Z0-9()@:%._+~#?&/=]+) that no remaining "pickle" substring appears in any real external URL repo-wide, other than the deliberately skip-listed pickle-dashboard-svc example. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_012uBgAMf3CkcrULiQQMJBTx --- .../urls_projectcalico.docs.tigera.io.txt | 6 +- __tests__/data/urls_with_canonicals.txt | 126 ++++++------- .../monitor/prometheus/byo-prometheus.mdx | 12 +- calico-cloud/reference/installation/_api.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 12 +- .../reference/installation/_api.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 12 +- .../reference/installation/_api.mdx | 2 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 4 +- .../components/UpgradeOperatorSimple.js | 2 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 4 +- .../kubernetes-upgrade-tsee/helm.mdx | 4 +- .../monitor/prometheus/byo-prometheus.mdx | 14 +- .../reference/installation/_api.mdx | 2 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 4 +- .../components/UpgradeOperatorSimple.js | 2 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 2 +- .../kubernetes-upgrade-tsee/helm.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 12 +- .../reference/installation/_api.mdx | 2 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 4 +- .../components/UpgradeOperatorSimple.js | 2 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 2 +- .../kubernetes-upgrade-tsee/helm.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 12 +- .../reference/installation/_api.mdx | 2 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 4 +- .../components/UpgradeOperatorSimple.js | 2 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 2 +- .../kubernetes-upgrade-tsee/helm.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 12 +- .../reference/installation/_api.mdx | 2 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 4 +- .../components/UpgradeOperatorSimple.js | 2 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 2 +- .../kubernetes-upgrade-tsee/helm.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 12 +- .../reference/installation/_api.mdx | 2 +- .../_includes/components/InstallAKS.js | 4 +- .../_includes/components/InstallEKS.js | 4 +- .../_includes/components/InstallGKE.js | 2 +- .../_includes/components/InstallGeneric.js | 2 +- .../components/OpenShiftPrometheusOperator.js | 4 +- .../components/UpgradeOperatorSimple.js | 2 +- .../install-on-clusters/docker-enterprise.mdx | 2 +- .../kubernetes/quickstart.mdx | 2 +- .../install-on-clusters/rancher.mdx | 2 +- .../install-on-clusters/rke2.mdx | 2 +- .../upgrade-to-tsee/helm.mdx | 4 +- .../kubernetes-upgrade-tsee/helm.mdx | 4 +- .../monitor/prometheus/byo-prometheus.mdx | 14 +- .../reference/installation/_api.mdx | 2 +- static/calico-cloud/llms-full.txt | 90 ++++----- static/calico-cloud/llms.txt | 14 +- static/calico-enterprise/llms-full.txt | 174 +++++++++--------- static/calico-enterprise/llms.txt | 16 +- .../licenses/third-party-attributions.html | 12 +- static/calico/3.26/licenses/index.html | 12 +- .../licenses/third-party-attributions.html | 32 ++-- .../licenses/third-party-attributions.html | 32 ++-- .../licenses/third-party-attributions.html | 32 ++-- .../licenses/third-party-attributions.html | 32 ++-- .../licenses/third-party-attributions.html | 60 +++--- .../licenses/third-party-attributions.html | 40 ++-- static/calico/llms-full.txt | 28 +-- static/calico/llms.txt | 6 +- 106 files changed, 515 insertions(+), 515 deletions(-) diff --git a/__tests__/data/urls_projectcalico.docs.tigera.io.txt b/__tests__/data/urls_projectcalico.docs.tigera.io.txt index c1b850a005..c0fd839b11 100644 --- a/__tests__/data/urls_projectcalico.docs.tigera.io.txt +++ b/__tests__/data/urls_projectcalico.docs.tigera.io.txt @@ -142,7 +142,7 @@ https://projectcalico.docs.tigera.io/getting-started/kubernetes/self-managed-pub https://projectcalico.docs.tigera.io/getting-started/openstack/installation/redhat https://projectcalico.docs.tigera.io/security/http-methods https://projectcalico.docs.tigera.io/reference/vpp/host-network -https://projectcalico.docs.tigera.io/reference/felix/pickle +https://projectcalico.docs.tigera.io/reference/felix/prometheus https://projectcalico.docs.tigera.io/getting-started/kubernetes/hardway/ https://projectcalico.docs.tigera.io/reference/public-cloud/aws https://projectcalico.docs.tigera.io/getting-started/kubernetes/flannel/ @@ -222,8 +222,8 @@ https://projectcalico.docs.tigera.io/getting-started/bare-metal/about https://projectcalico.docs.tigera.io/reference/calicoctl/overview https://projectcalico.docs.tigera.io/reference/etcd-rbac/certificate-generation https://projectcalico.docs.tigera.io/getting-started/bare-metal/installation/binary-mgr -https://projectcalico.docs.tigera.io/reference/kube-controllers/pickle -https://projectcalico.docs.tigera.io/reference/typha/pickle +https://projectcalico.docs.tigera.io/reference/kube-controllers/prometheus +https://projectcalico.docs.tigera.io/reference/typha/prometheus https://projectcalico.docs.tigera.io/reference/architecture/design/l2-interconnect-fabric https://projectcalico.docs.tigera.io/reference/calicoctl/node/ https://projectcalico.docs.tigera.io/maintenance/clis/calicoctl/install#install-calicoctl-as-a-binary-on-a-single-host diff --git a/__tests__/data/urls_with_canonicals.txt b/__tests__/data/urls_with_canonicals.txt index c3b9c5aaff..f8d03eb342 100644 --- a/__tests__/data/urls_with_canonicals.txt +++ b/__tests__/data/urls_with_canonicals.txt @@ -20,7 +20,7 @@ https://docs.tigera.io/v3.8/about/about-calico-enterprise/ https://docs.tigera.io/v3.12/security/aws-integration/aws-security-group-integration https://docs.tigera.io/v3.11/release-notes/ https://docs.tigera.io/v3.9/getting-started/bare-metal/installation/container -https://docs.tigera.io/v3.7/reference/felix/pickle +https://docs.tigera.io/v3.7/reference/felix/prometheus https://docs.tigera.io/v3.7/maintenance/performance/ https://docs.tigera.io/v3.7/compliance/compliance-reports/overview https://docs.tigera.io/v3.7/networking/ @@ -93,7 +93,7 @@ https://docs.tigera.io/v3.7/reference/resources/hostendpoint https://docs.tigera.io/v3.7/getting-started/bare-metal/installation/binary https://docs.tigera.io/v3.7/networking/ipv6 https://docs.tigera.io/v3.0/getting-started/ -https://docs.tigera.io/v3.0/maintenance/monitor/pickle +https://docs.tigera.io/v3.0/maintenance/monitor/prometheus https://docs.tigera.io/v3.7/reference/resources/workloadendpoint https://docs.tigera.io/v3.0/security/logs/elastic/dns https://docs.tigera.io/v3.7/getting-started/kubernetes/requirements @@ -293,7 +293,7 @@ https://docs.tigera.io/v3.7/getting-started/cnx/roles-and-permissions https://docs.tigera.io/v3.7/security/aws-integration/tiers-and-policy https://docs.tigera.io/v3.7/reference/calicoctl/create https://docs.tigera.io/v3.7/maintenance/troubleshoot/component-logs -https://docs.tigera.io/v3.7/reference/kube-controllers/pickle +https://docs.tigera.io/v3.7/reference/kube-controllers/prometheus https://docs.tigera.io/v3.7/reference/resources/networkpolicy https://docs.tigera.io/v3.7/multicluster/federation/aws https://docs.tigera.io/v3.7/visibility/iptables @@ -303,13 +303,13 @@ https://docs.tigera.io/v3.0/reference/typha/configuration https://docs.tigera.io/v3.0/reference/resources/networkpolicy https://docs.tigera.io/v3.0/reference/resources/profile https://docs.tigera.io/v3.0/reference/calicoctl/create -https://docs.tigera.io/v3.7/maintenance/monitor/pickle +https://docs.tigera.io/v3.7/maintenance/monitor/prometheus https://docs.tigera.io/v3.7/security/tutorials/kubernetes-policy-basic https://docs.tigera.io/v3.0/getting-started/bare-metal/installation/container https://docs.tigera.io/v3.7/reference/cni-plugin/configuration https://docs.tigera.io/v3.0/reference/felix/ https://docs.tigera.io/v3.7/reference/host-endpoints/pre-dnat -https://docs.tigera.io/v3.0/reference/felix/pickle +https://docs.tigera.io/v3.0/reference/felix/prometheus https://docs.tigera.io/v3.7/reference/calicoq/overview https://docs.tigera.io/v3.7/networking/mtu https://docs.tigera.io/v3.0/security/tutorials/protect-hosts @@ -625,7 +625,7 @@ https://docs.tigera.io/v3.11/multicluster/federation/ https://docs.tigera.io/v3.13/threat/web-application-firewall https://docs.tigera.io/v3.13/security/tutorials/kubernetes-policy-basic https://docs.tigera.io/v3.11/reference/attribution/attribution -https://docs.tigera.io/v3.6/reference/kube-controllers/pickle +https://docs.tigera.io/v3.6/reference/kube-controllers/prometheus https://docs.tigera.io/v3.6/threat/honeypod/honeypod-controller https://docs.tigera.io/v3.1/reference/calicoctl/node/diags https://docs.tigera.io/v2.7/reference/public-cloud/ @@ -761,7 +761,7 @@ https://docs.tigera.io/v3.3/reference/calicoctl/ipam/show https://docs.tigera.io/v3.1/reference/ https://docs.tigera.io/v3.9/reference/resources/remoteclusterconfiguration https://docs.tigera.io/v3.6/reference/calicoctl/label -https://docs.tigera.io/v3.9/reference/felix/pickle +https://docs.tigera.io/v3.9/reference/felix/prometheus https://docs.tigera.io/v2.7/security/comms/crypto-auth https://docs.tigera.io/v3.13/maintenance/clis/calicoctl/configure/ https://docs.tigera.io/v2.7/reference/architecture/design/l2-interconnect-fabric @@ -793,7 +793,7 @@ https://docs.tigera.io/v3.12/getting-started/calico-enterprise https://docs.tigera.io/v3.12/getting-started/cnx/roles-and-permissions https://docs.tigera.io/v3.9/reference/calicoctl/captured-packets https://docs.tigera.io/v3.9/security/policy-firewalls/ -https://docs.tigera.io/v3.3/maintenance/monitor/pickle +https://docs.tigera.io/v3.3/maintenance/monitor/prometheus https://docs.tigera.io/v3.13/reference/calicoctl/delete https://docs.tigera.io/v3.2/networking/ https://docs.tigera.io/v3.12/reference/calicoq/selectors @@ -830,7 +830,7 @@ https://docs.tigera.io/v3.5/threat/anomaly-detection/customizing https://docs.tigera.io/v3.11/getting-started/windows-calico/ https://docs.tigera.io/v3.4/maintenance/upgrading-calico-to-calico-enterprise https://docs.tigera.io/v3.9/networking/ipv6-control-plane -https://docs.tigera.io/v3.9/maintenance/monitor/pickle/pickle +https://docs.tigera.io/v3.9/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/v3.13/reference/resources/globalnetworkset https://docs.tigera.io/v3.9/security/fortinet-integration/overview https://docs.tigera.io/v3.2/reference/public-cloud/gce @@ -844,13 +844,13 @@ https://docs.tigera.io/v3.13/getting-started/kubernetes/quickstart https://docs.tigera.io/v3.13/reference/calicoctl/ipam/show https://docs.tigera.io/v3.9/reference/calicoctl/node/status https://docs.tigera.io/v3.4/getting-started/windows-calico/limitations -https://docs.tigera.io/v3.5/maintenance/monitor/pickle +https://docs.tigera.io/v3.5/maintenance/monitor/prometheus https://docs.tigera.io/v2.7/reference/host-endpoints/forwarded https://docs.tigera.io/v3.9/maintenance/logstorage/ https://docs.tigera.io/v2.8/reference/resources/licensekey https://docs.tigera.io/v3.2/security/simple-policy-cnx -https://docs.tigera.io/v3.13/reference/felix/pickle -https://docs.tigera.io/v3.4/maintenance/monitor/pickle +https://docs.tigera.io/v3.13/reference/felix/prometheus +https://docs.tigera.io/v3.4/maintenance/monitor/prometheus https://docs.tigera.io/v3.13/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.5/getting-started/cnx/access-the-manager https://docs.tigera.io/v3.13/networking/vxlan-ipip @@ -861,7 +861,7 @@ https://docs.tigera.io/v3.1/reference/resources/workloadendpoint https://docs.tigera.io/v3.11/security/panorama-integration/tigera-panorama-address-groups https://docs.tigera.io/v3.5/maintenance/performance/ebpf/ https://docs.tigera.io/v3.3/getting-started/bare-metal/about -https://docs.tigera.io/v3.13/maintenance/monitor/pickle/alertmanager +https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/alertmanager https://docs.tigera.io/v3.9/visibility/elastic/flow/datatypes https://docs.tigera.io/v3.13/policy/ https://docs.tigera.io/v3.12/getting-started/openshift/requirements @@ -957,7 +957,7 @@ https://docs.tigera.io/v3.6/getting-started/bare-metal/installation/ https://docs.tigera.io/v3.2/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.9/getting-started/kubernetes/gke https://docs.tigera.io/v3.13/reference/calicoq/endpoint -https://docs.tigera.io/v3.13/maintenance/monitor/pickle/pickle +https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/v3.2/reference/host-endpoints/summary https://docs.tigera.io/v3.11/security/fortinet-integration/firewall-integration https://docs.tigera.io/v3.9/threat/tor-vpn-feed-and-dashboard @@ -973,7 +973,7 @@ https://docs.tigera.io/v3.6/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/v3.12/compliance/compliance-reports-cis https://docs.tigera.io/v3.2/reference/calicoctl/patch https://docs.tigera.io/v3.3/reference/calicoctl/convert -https://docs.tigera.io/v2.7/reference/felix/pickle +https://docs.tigera.io/v2.7/reference/felix/prometheus https://docs.tigera.io/v3.12/networking/custom-bgp-config https://docs.tigera.io/v3.6/networking/workloads-outside-cluster https://docs.tigera.io/v3.11/reference/host-endpoints/summary @@ -1029,13 +1029,13 @@ https://docs.tigera.io/v3.13/security/default-deny https://docs.tigera.io/v3.13/getting-started/windows-calico/troubleshoot https://docs.tigera.io/v3.6/threat/ingress https://docs.tigera.io/v3.13/maintenance/logstorage/log-storage-recommendations -https://docs.tigera.io/v3.5/reference/felix/pickle +https://docs.tigera.io/v3.5/reference/felix/prometheus https://docs.tigera.io/v3.1/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/v3.6/multicluster/ https://docs.tigera.io/v3.13/security/external-ips-policy https://docs.tigera.io/v3.13/threat/honeypod/honeypod-controller https://docs.tigera.io/v3.5/multicluster/federation/ -https://docs.tigera.io/v3.12/maintenance/monitor/pickle/alertmanager +https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/alertmanager https://docs.tigera.io/v3.6/getting-started/private-registry/private-registry-image-path https://docs.tigera.io/v3.13/security/fortinet-integration/overview https://docs.tigera.io/v3.9/threat/anomaly-detection/overview @@ -1149,7 +1149,7 @@ https://docs.tigera.io/v3.6/getting-started/openshift/ https://docs.tigera.io/v3.12/reference/host-endpoints/failsafe https://docs.tigera.io/v2.7/reference/calicoq/overview https://docs.tigera.io/v3.9/visibility/alerts -https://docs.tigera.io/v3.11/maintenance/monitor/pickle/alertmanager +https://docs.tigera.io/v3.11/maintenance/monitor/prometheus/alertmanager https://docs.tigera.io/v3.3/reference/resources/managedcluster https://docs.tigera.io/v3.4/reference/calicoctl/replace https://docs.tigera.io/v3.13/security/policy-firewalls/ @@ -1321,7 +1321,7 @@ https://docs.tigera.io/v3.9/reference/cni-plugin/configuration https://docs.tigera.io/v2.8/networking/assign-ip-addresses-topology https://docs.tigera.io/v3.12/networking/ipv6 https://docs.tigera.io/v3.9/getting-started/install-on-clusters/ -https://docs.tigera.io/v3.12/maintenance/monitor/pickle/byo-pickle +https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/byo-prometheus https://docs.tigera.io/v3.9/visibility/elastic/bgp https://docs.tigera.io/v3.4/reference/resources/packetcapture https://docs.tigera.io/v3.13/multicluster/federation/overview @@ -1412,7 +1412,7 @@ https://docs.tigera.io/v3.11/security/ https://docs.tigera.io/v3.13/getting-started/cnx/authentication-quickstart https://docs.tigera.io/v2.7/security/logs/elastic/dns https://docs.tigera.io/v3.12/networking/mtu -https://docs.tigera.io/v3.11/maintenance/monitor/pickle/pickle +https://docs.tigera.io/v3.11/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/v3.12/security/simple-policy-cnx https://docs.tigera.io/v3.6/reference/host-endpoints/summary https://docs.tigera.io/v3.11/about/about-calico-enterprise @@ -1433,7 +1433,7 @@ https://docs.tigera.io/v3.2/getting-started/private-registry/private-registry-re https://docs.tigera.io/v3.13/security/training/about-kubernetes-services https://docs.tigera.io/v3.13/reference/resources/deeppacketinspection https://docs.tigera.io/v3.9/security/training/about-network-policy -https://docs.tigera.io/v3.13/maintenance/monitor/pickle/ +https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/ https://docs.tigera.io/v3.4/reference/public-cloud/gce https://docs.tigera.io/v3.9/threat/honeypod/ https://docs.tigera.io/v3.11/reference/host-endpoints/failsafe @@ -1586,7 +1586,7 @@ https://docs.tigera.io/v3.9/security/beginners https://docs.tigera.io/v3.13/reference/host-endpoints/pre-dnat https://docs.tigera.io/v3.9/security/ https://docs.tigera.io/v3.12/reference/resources/overview -https://docs.tigera.io/v3.12/maintenance/monitor/pickle/ +https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/ https://docs.tigera.io/v3.11/security/aws-integration/get-started https://docs.tigera.io/v3.11/reference/calicoctl/captured-packets https://docs.tigera.io/v3.12/security/comms/crypto-auth @@ -1618,7 +1618,7 @@ https://docs.tigera.io/v3.12/networking/bgp https://docs.tigera.io/v3.5/security/kubernetes-nodes https://docs.tigera.io/v3.13/reference/calicoctl/ipam/configure https://docs.tigera.io/v3.5/visibility/elastic/flow/datatypes -https://docs.tigera.io/v3.4/reference/felix/pickle +https://docs.tigera.io/v3.4/reference/felix/prometheus https://docs.tigera.io/v3.12/multicluster/federation/aws https://docs.tigera.io/v3.5/maintenance/upgrading-calico-to-calico-enterprise https://docs.tigera.io/v3.9/reference/calicoctl/version @@ -1695,7 +1695,7 @@ https://docs.tigera.io/v3.13/networking/bgp https://docs.tigera.io/v3.13/getting-started/windows-calico/kubernetes/standard https://docs.tigera.io/v3.9/reference/resources/profile https://docs.tigera.io/v3.13/threat/ -https://docs.tigera.io/v3.11/maintenance/monitor/pickle/ +https://docs.tigera.io/v3.11/maintenance/monitor/prometheus/ https://docs.tigera.io/v3.11/multicluster/mcm/fine-tune-deployment https://docs.tigera.io/v3.9/multicluster/mcm/configure https://docs.tigera.io/v3.3/reference/resources/kubecontrollersconfig @@ -1704,13 +1704,13 @@ https://docs.tigera.io/v3.11/networking/ipv6 https://docs.tigera.io/v3.13/threat/suspicious-ips https://docs.tigera.io/v3.9/security/fortinet-integration/firewall-integration https://docs.tigera.io/v3.12/reference/calicoctl/node/diags -https://docs.tigera.io/v3.6/reference/felix/pickle +https://docs.tigera.io/v3.6/reference/felix/prometheus https://docs.tigera.io/v3.11/threat/anomaly-detection/monitoring https://docs.tigera.io/v3.6/reference/host-endpoints/overview https://docs.tigera.io/v2.7/reference/cni-plugin/configuration https://docs.tigera.io/v3.4/security/aws-integration/metadata-access https://docs.tigera.io/v3.2/reference/host-endpoints/objects -https://docs.tigera.io/v3.12/reference/kube-controllers/pickle +https://docs.tigera.io/v3.12/reference/kube-controllers/prometheus https://docs.tigera.io/v3.12/threat/ https://docs.tigera.io/v3.13/maintenance/clis/calicoq/configure/overview https://docs.tigera.io/v2.7/reference/calicoq/version @@ -1757,7 +1757,7 @@ https://docs.tigera.io/v3.13/getting-started/windows-calico/kubernetes/requireme https://docs.tigera.io/v3.13/reference/calicoq/selectors https://docs.tigera.io/v3.11/visibility/elastic/rbac-elasticsearch https://docs.tigera.io/v3.9/getting-started/windows-calico/demo -https://docs.tigera.io/v3.13/maintenance/monitor/pickle/byo-pickle +https://docs.tigera.io/v3.13/maintenance/monitor/prometheus/byo-prometheus https://docs.tigera.io/v3.4/security/aws-integration/tiers-and-policy https://docs.tigera.io/v3.1/reference/architecture/overview https://docs.tigera.io/v3.11/visibility/iptables @@ -1799,7 +1799,7 @@ https://docs.tigera.io/v3.11/visibility/elastic/dns/filtering-dns https://docs.tigera.io/v3.6/visibility/elastic/filtering-dns https://docs.tigera.io/v3.13/visibility/elastic/flow/hep https://docs.tigera.io/v3.11/maintenance/kubernetes-upgrade-tsee/operator -https://docs.tigera.io/v3.6/maintenance/monitor/pickle +https://docs.tigera.io/v3.6/maintenance/monitor/prometheus https://docs.tigera.io/v3.6/reference/calicoctl/datastore/migrate/unlock https://docs.tigera.io/v3.12/visibility/elastic/bgp https://docs.tigera.io/v3.3/getting-started/openshift/requirements @@ -1843,7 +1843,7 @@ https://docs.tigera.io/v3.6/security/aws-integration/aws-security-group-integrat https://docs.tigera.io/v3.4/security/fortinet-integration/fortimgr-integration https://docs.tigera.io/v3.11/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.13/visibility/elastic/audit-overview -https://docs.tigera.io/v3.2/maintenance/monitor/pickle +https://docs.tigera.io/v3.2/maintenance/monitor/prometheus https://docs.tigera.io/v3.3/reference/resources/overview https://docs.tigera.io/v3.9/reference/resources/packetcapture https://docs.tigera.io/v3.9/reference/calicoctl/delete @@ -1873,7 +1873,7 @@ https://docs.tigera.io/v3.4/reference/resources/kubecontrollersconfig https://docs.tigera.io/v3.3/security/logs/elastic/view https://docs.tigera.io/v3.12/reference/calicoctl/version https://docs.tigera.io/v3.9/networking/bgp -https://docs.tigera.io/v3.9/maintenance/monitor/pickle/ +https://docs.tigera.io/v3.9/maintenance/monitor/prometheus/ https://docs.tigera.io/v3.9/networking/mtu https://docs.tigera.io/v3.9/reference/calicoctl/node/run https://docs.tigera.io/v3.5/visibility/elastic/filtering-dns @@ -1883,7 +1883,7 @@ https://docs.tigera.io/v2.7/getting-started/bare-metal/installation/container https://docs.tigera.io/v3.13/reference/faq https://docs.tigera.io/v3.12/compliance/ https://docs.tigera.io/v3.5/reference/calicoctl/node/diags -https://docs.tigera.io/v3.12/reference/felix/pickle +https://docs.tigera.io/v3.12/reference/felix/prometheus https://docs.tigera.io/v3.9/networking/training/about-kubernetes-networking https://docs.tigera.io/v3.13/getting-started/private-registry/private-registry-regular https://docs.tigera.io/v3.13/getting-started/kubernetes/rancher @@ -1941,7 +1941,7 @@ https://docs.tigera.io/v2.7/getting-started/kubernetes/requirements https://docs.tigera.io/v3.4/getting-started/kubernetes/aks https://docs.tigera.io/v3.9/security/comms/secure-bgp https://docs.tigera.io/v3.6/maintenance/troubleshoot/component-logs -https://docs.tigera.io/v3.9/reference/kube-controllers/pickle +https://docs.tigera.io/v3.9/reference/kube-controllers/prometheus https://docs.tigera.io/v3.9/reference/ https://docs.tigera.io/v3.11/visibility/elastic/retention https://docs.tigera.io/v3.13/reference/host-endpoints/summary @@ -2045,7 +2045,7 @@ https://docs.tigera.io/v3.5/getting-started/openshift/ https://docs.tigera.io/v3.3/maintenance/clis/calicoctl/install https://docs.tigera.io/v3.11/maintenance/decommissioning-a-node https://docs.tigera.io/v3.5/getting-started/private-registry/private-registry-regular -https://docs.tigera.io/v3.11/reference/felix/pickle +https://docs.tigera.io/v3.11/reference/felix/prometheus https://docs.tigera.io/v3.9/multicluster/federation/services-controller https://docs.tigera.io/v3.11/reference/public-cloud/ https://docs.tigera.io/v3.13/maintenance/ebpf/ @@ -2192,7 +2192,7 @@ https://docs.tigera.io/v3.11/reference/calicoctl/node/overview https://docs.tigera.io/v3.13/reference/felix/ https://docs.tigera.io/v3.4/getting-started/openshift/ https://docs.tigera.io/v3.9/reference/component-resources/ -https://docs.tigera.io/v3.11/reference/kube-controllers/pickle +https://docs.tigera.io/v3.11/reference/kube-controllers/prometheus https://docs.tigera.io/v3.13/security/tutorials/kubernetes-policy-advanced https://docs.tigera.io/v3.2/security/aws-integration/metadata-access https://docs.tigera.io/v3.12/security/fortinet-integration/fortimgr-integration @@ -2235,12 +2235,12 @@ https://docs.tigera.io/v3.11/reference/faq https://docs.tigera.io/v3.5/visibility/elastic/l7/datatypes https://docs.tigera.io/v3.13/getting-started/ https://docs.tigera.io/v3.12/visibility/elastic/flow/ -https://docs.tigera.io/v3.12/maintenance/monitor/pickle/pickle +https://docs.tigera.io/v3.12/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/v3.12/reference/public-cloud/gce -https://docs.tigera.io/v3.1/reference/felix/pickle +https://docs.tigera.io/v3.1/reference/felix/prometheus https://docs.tigera.io/v3.1/security/ingress https://docs.tigera.io/v3.9/reference/calicoctl/datastore/overview -https://docs.tigera.io/v3.13/reference/kube-controllers/pickle +https://docs.tigera.io/v3.13/reference/kube-controllers/prometheus https://docs.tigera.io/v3.11/maintenance/clis/calicoctl/configure/ https://docs.tigera.io/v3.9/maintenance/clis/calicoctl/configure/ https://docs.tigera.io/v3.3/reference/calicoctl/node/status @@ -2352,7 +2352,7 @@ https://docs.tigera.io/v2.8/networking/custom-bgp-config https://docs.tigera.io/v3.5/maintenance/logstorage/log-storage-requirements https://docs.tigera.io/v3.13/maintenance/decommissioning-a-node https://docs.tigera.io/v3.6/maintenance/troubleshoot/troubleshoot-ebpf -https://docs.tigera.io/v3.9/maintenance/monitor/pickle/alertmanager +https://docs.tigera.io/v3.9/maintenance/monitor/prometheus/alertmanager https://docs.tigera.io/v3.6/getting-started/bare-metal/installation/container https://docs.tigera.io/v3.6/getting-started/kubernetes/gke https://docs.tigera.io/v3.12/multicluster/mcm/fine-tune-deployment @@ -2493,7 +2493,7 @@ https://docs.tigera.io/v3.8/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/v3.10/maintenance/monitor/metrics/license-agent https://docs.tigera.io/v3.8/reference/resources/globalnetworkpolicy https://docs.tigera.io/v3.8/reference/calicoctl/replace -https://docs.tigera.io/v3.8/maintenance/monitor/pickle/pickle +https://docs.tigera.io/v3.8/maintenance/monitor/prometheus/prometheus https://docs.tigera.io/v3.8/visibility/elastic/archive-storage https://docs.tigera.io/v3.8/getting-started/bare-metal/ https://docs.tigera.io/v3.10/maintenance/logstorage/ @@ -2582,7 +2582,7 @@ https://docs.tigera.io/v3.10/security/aws-integration/get-started https://docs.tigera.io/v3.10/reference/calicoctl/ipam/check https://docs.tigera.io/v3.8/getting-started/kubernetes/quickstart https://docs.tigera.io/v3.10/reference/dikastes/configuration -https://docs.tigera.io/v3.10/reference/kube-controllers/pickle +https://docs.tigera.io/v3.10/reference/kube-controllers/prometheus https://docs.tigera.io/v3.8/security/tutorials/kubernetes-policy-advanced https://docs.tigera.io/v3.10/reference/resources/workloadendpoint https://docs.tigera.io/v3.8/security/ @@ -2623,7 +2623,7 @@ https://docs.tigera.io/v3.10/getting-started/install-on-clusters/ https://docs.tigera.io/v3.8/reference/felix/ https://docs.tigera.io/v3.8/reference/resources/workloadendpoint https://docs.tigera.io/v3.10/threat/ -https://docs.tigera.io/v3.10/reference/felix/pickle +https://docs.tigera.io/v3.10/reference/felix/prometheus https://docs.tigera.io/v3.8/reference/calicoq/policy https://docs.tigera.io/v3.8/reference/architecture/design/l3-interconnect-fabric https://docs.tigera.io/v3.10/reference/calicoctl/ipam/release @@ -2664,7 +2664,7 @@ https://docs.tigera.io/v3.8/maintenance/troubleshoot/ https://docs.tigera.io/v3.10/security/comms/certificate-management https://docs.tigera.io/v3.8/security/tiered-policy https://docs.tigera.io/v3.10/reference/host-endpoints/objects -https://docs.tigera.io/v3.8/reference/felix/pickle +https://docs.tigera.io/v3.8/reference/felix/prometheus https://docs.tigera.io/v3.10/reference/public-cloud/azure https://docs.tigera.io/v3.10/visibility/elastic/kube-audit https://docs.tigera.io/v3.10/policy/ @@ -2704,11 +2704,11 @@ https://docs.tigera.io/v3.10/maintenance/clis/calicoctl/ https://docs.tigera.io/v3.8/threat/suspicious-ips https://docs.tigera.io/v3.8/security/comms/crypto-auth https://docs.tigera.io/v3.10/maintenance/monitor/metrics/bgp-metrics -https://docs.tigera.io/v3.8/maintenance/monitor/pickle/ +https://docs.tigera.io/v3.8/maintenance/monitor/prometheus/ https://docs.tigera.io/v3.8/maintenance/ebpf/ https://docs.tigera.io/v3.8/security/tutorials/kubernetes-policy-basic https://docs.tigera.io/v3.10/reference/resources/globalnetworkpolicy -https://docs.tigera.io/v3.8/maintenance/monitor/pickle/alertmanager +https://docs.tigera.io/v3.8/maintenance/monitor/prometheus/alertmanager https://docs.tigera.io/v3.10/about/about-calico-enterprise https://docs.tigera.io/v3.8/security/tutorials/app-layer-policy/enforce-policy-istio https://docs.tigera.io/v3.8/getting-started/private-registry/private-registry-image-path @@ -3013,7 +3013,7 @@ https://docs.tigera.io/archive/v3.18/reference/etcd-rbac/calico-etcdv3-paths https://docs.tigera.io/archive/v3.22/getting-started/windows-calico/demo https://docs.tigera.io/archive/v3.19/security/tutorials/kubernetes-policy-advanced https://docs.tigera.io/archive/v3.17/reference/calicoctl/node/status -https://docs.tigera.io/archive/v3.13/reference/felix/pickle +https://docs.tigera.io/archive/v3.13/reference/felix/prometheus https://docs.tigera.io/archive/v3.22/maintenance/install-apiserver https://docs.tigera.io/archive/v3.19/reference/calicoctl/patch https://docs.tigera.io/archive/v3.19/getting-started/bare-metal/installation/binary @@ -3242,7 +3242,7 @@ https://docs.tigera.io/archive/v3.14/getting-started/kubernetes/installation/con https://docs.tigera.io/archive/v3.19/getting-started/kubernetes/hardway/configure-bgp-peering https://docs.tigera.io/archive/v3.20/reference/calicoctl/node/overview https://docs.tigera.io/archive/v3.17/reference/architecture/overview -https://docs.tigera.io/v3.12/maintenance/monitor/pickle +https://docs.tigera.io/v3.12/maintenance/monitor/prometheus https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/hardway/the-calico-datastore https://docs.tigera.io/archive/v3.12/reference/typha/configuration https://docs.tigera.io/archive/v3.19/reference/calicoctl/replace @@ -3273,7 +3273,7 @@ https://docs.tigera.io/archive/v3.23/reference/resources/node https://docs.tigera.io/archive/v3.15/getting-started/openshift/installation https://docs.tigera.io/archive/v3.22/reference/calicoctl/get https://docs.tigera.io/archive/v3.23/reference/public-cloud/ -https://docs.tigera.io/archive/v3.22/reference/kube-controllers/pickle +https://docs.tigera.io/archive/v3.22/reference/kube-controllers/prometheus https://docs.tigera.io/archive/v3.19/reference/host-endpoints/connectivity https://docs.tigera.io/archive/v3.20/security/kubernetes-default-deny https://docs.tigera.io/archive/v3.22/maintenance/troubleshoot/troubleshooting @@ -3288,7 +3288,7 @@ https://docs.tigera.io/archive/v3.21/reference/legal/node https://docs.tigera.io/archive/v3.22/reference/host-endpoints/summary https://docs.tigera.io/archive/v3.12/networking/ https://docs.tigera.io/archive/v3.13/reference/architecture/overview -https://docs.tigera.io/archive/v3.20/reference/felix/pickle +https://docs.tigera.io/archive/v3.20/reference/felix/prometheus https://docs.tigera.io/archive/v3.20/security/tutorials/protect-hosts https://docs.tigera.io/archive/v3.14/networking/openstack/configuration https://docs.tigera.io/archive/v3.12/security/comms/reduce-nodes @@ -3427,7 +3427,7 @@ https://docs.tigera.io/archive/v3.13/reference/host-endpoints/pre-dnat https://docs.tigera.io/archive/v3.15/reference/calicoctl/node/diags https://docs.tigera.io/archive/v3.22/reference/calicoctl/delete https://docs.tigera.io/archive/v3.19/getting-started/windows-calico/openshift/ -https://docs.tigera.io/archive/v3.14/reference/felix/pickle +https://docs.tigera.io/archive/v3.14/reference/felix/prometheus https://docs.tigera.io/archive/v3.22/reference/faq https://docs.tigera.io/archive/v3.18/getting-started/kubernetes/hardway/configure-ip-pools https://docs.tigera.io/archive/v3.22/reference/resources/networkpolicy @@ -3483,7 +3483,7 @@ https://docs.tigera.io/archive/v3.15/getting-started/openstack/requirements https://docs.tigera.io/archive/v3.22/getting-started/windows-calico/limitations https://docs.tigera.io/archive/v3.16/reference/etcd-rbac/kubernetes-advanced https://docs.tigera.io/archive/v3.13/reference/calicoctl/apply -https://docs.tigera.io/archive/v3.15/reference/felix/pickle +https://docs.tigera.io/archive/v3.15/reference/felix/prometheus https://docs.tigera.io/archive/v3.16/getting-started/clis/calicoctl/ https://docs.tigera.io/archive/v3.14/networking/bgp https://docs.tigera.io/archive/v3.16/reference/host-endpoints/failsafe @@ -3573,7 +3573,7 @@ https://docs.tigera.io/archive/v3.22/getting-started/kubernetes/hardway/install- https://docs.tigera.io/archive/v3.22/maintenance/troubleshoot/commands https://docs.tigera.io/archive/v3.20/getting-started/kubernetes/k3s/multi-node-install https://docs.tigera.io/archive/v3.22/security/comms/ -https://docs.tigera.io/archive/v3.22/reference/felix/pickle +https://docs.tigera.io/archive/v3.22/reference/felix/prometheus https://docs.tigera.io/archive/v3.21/getting-started/openstack/installation/ubuntu https://docs.tigera.io/archive/v3.13/reference/faq https://docs.tigera.io/archive/v3.13/maintenance/kubernetes-upgrade @@ -3987,15 +3987,15 @@ https://docs.tigera.io/archive/v3.20/getting-started/windows-calico/openshift/in https://docs.tigera.io/archive/v3.16/reference/public-cloud/azure https://docs.tigera.io/archive/v3.18/networking/openstack/dev-machine-setup https://docs.tigera.io/archive/v3.18/networking/ipv6 -https://docs.tigera.io/archive/v3.23/reference/felix/pickle +https://docs.tigera.io/archive/v3.23/reference/felix/prometheus https://docs.tigera.io/archive/v3.22/release-notes/ https://docs.tigera.io/archive/v3.23/reference/host-endpoints/forwarded -https://docs.tigera.io/archive/v3.18/reference/kube-controllers/pickle +https://docs.tigera.io/archive/v3.18/reference/kube-controllers/prometheus https://docs.tigera.io/v3.12/getting-started/openshift/installation/index https://docs.tigera.io/archive/v3.20/getting-started/kubernetes/installation/config-options https://docs.tigera.io/archive/v3.12/reference/dikastes/configuration https://docs.tigera.io/archive/v3.20/reference/etcd-rbac/calico-etcdv3-paths -https://docs.tigera.io/archive/v3.20/reference/kube-controllers/pickle +https://docs.tigera.io/archive/v3.20/reference/kube-controllers/prometheus https://docs.tigera.io/archive/v3.22/getting-started/openstack/installation/overview https://docs.tigera.io/archive/v3.12/reference/involved https://docs.tigera.io/archive/v3.13/networking/use-ipvs @@ -4015,7 +4015,7 @@ https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/installation/con https://docs.tigera.io/archive/v3.20/reference/legal/node https://docs.tigera.io/v3.12/maintenance/monitor/metrics https://docs.tigera.io/archive/v3.21/getting-started/kubernetes/hardway/configure-bgp-peering -https://docs.tigera.io/archive/v3.23/reference/kube-controllers/pickle +https://docs.tigera.io/archive/v3.23/reference/kube-controllers/prometheus https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/hardway/configure-ip-pools https://docs.tigera.io/archive/v3.18/getting-started/kubernetes/hardway/install-node https://docs.tigera.io/v3.9/reference @@ -4054,7 +4054,7 @@ https://docs.tigera.io/archive/v3.19/networking/workloads-outside-cluster https://docs.tigera.io/v3.7/getting-started/cnx//access-the-manager https://docs.tigera.io/archive/v3.20/reference/calicoctl/create https://docs.tigera.io/archive/v3.21/networking/openstack/ -https://docs.tigera.io/v3.13/maintenance/monitor/pickle +https://docs.tigera.io/v3.13/maintenance/monitor/prometheus https://docs.tigera.io/archive/v3.12/getting-started/openshift/ https://docs.tigera.io/archive/v3.12/getting-started/bare-metal/installation/binary https://docs.tigera.io/archive/v3.17/reference/resources/globalnetworkset @@ -4075,7 +4075,7 @@ https://docs.tigera.io/archive/v3.17/getting-started/windows-calico/kubernetes/r https://docs.tigera.io/archive/v3.21/reference/etcd-rbac/overview https://docs.tigera.io/archive/v3.14/reference/host-endpoints/pre-dnat https://docs.tigera.io/archive/v3.22/getting-started/kubernetes/k3s/multi-node-install -https://docs.tigera.io/archive/v3.21/reference/kube-controllers/pickle +https://docs.tigera.io/archive/v3.21/reference/kube-controllers/prometheus https://docs.tigera.io/archive/v3.14/reference/calicoctl/ipam/configure https://docs.tigera.io/archive/v3.12/reference/resources/felixconfig https://docs.tigera.io/archive/v3.14/reference/calicoctl/ipam/overview @@ -4148,7 +4148,7 @@ https://docs.tigera.io/archive/v3.23/getting-started/kubernetes/minikube https://docs.tigera.io/archive/v3.13/reference/host-endpoints/selector https://docs.tigera.io/archive/v3.23/reference/legal/node https://docs.tigera.io/archive/v3.12/getting-started/openstack/requirements -https://docs.tigera.io/archive/v3.12/reference/felix/pickle +https://docs.tigera.io/archive/v3.12/reference/felix/prometheus https://docs.tigera.io/archive/v3.17/getting-started/kubernetes/hardway/install-node https://docs.tigera.io/archive/v3.14/reference/calicoctl/ipam/release https://docs.tigera.io/archive/v3.23/maintenance/clis/calicoctl @@ -4246,7 +4246,7 @@ https://docs.tigera.io/archive/v3.15/reference/calicoctl/ipam/release https://docs.tigera.io/archive/v3.22/networking/openstack/semantics https://docs.tigera.io/archive/v3.21/networking/openstack/configuration https://docs.tigera.io/archive/v3.20/security/ -https://docs.tigera.io/archive/v3.18/reference/felix/pickle +https://docs.tigera.io/archive/v3.18/reference/felix/prometheus https://docs.tigera.io/archive/v3.22/getting-started/openshift/requirements https://docs.tigera.io/archive/v3.23/reference/ https://docs.tigera.io/archive/v3.23/getting-started/windows-calico/kubernetes/requirements @@ -4348,7 +4348,7 @@ https://docs.tigera.io/archive/v3.19/maintenance/openstack-upgrade https://docs.tigera.io/archive/v3.22/reference/resources/networkset https://docs.tigera.io/archive/v3.12/reference/calicoctl/overview https://docs.tigera.io/archive/v3.23/security/tutorials/kubernetes-policy-advanced -https://docs.tigera.io/archive/v3.19/reference/felix/pickle +https://docs.tigera.io/archive/v3.19/reference/felix/prometheus https://docs.tigera.io/archive/v3.20/networking https://docs.tigera.io/archive/v3.15/getting-started/kubernetes/hardway/the-calico-datastore https://docs.tigera.io/archive/v3.23/getting-started/openstack/verification @@ -4391,7 +4391,7 @@ https://docs.tigera.io/archive/v3.14/security/tutorials/app-layer-policy/enforce https://docs.tigera.io/archive/v3.21/getting-started/kubernetes/helm https://docs.tigera.io/archive/v3.16/getting-started/kubernetes/hardway/install-typha https://docs.tigera.io/archive/v3.23/getting-started/kubernetes/hardway/istio-integration -https://docs.tigera.io/v3.11/maintenance/monitor/pickle +https://docs.tigera.io/v3.11/maintenance/monitor/prometheus https://docs.tigera.io/archive/v3.15/reference/resources/networkpolicy https://docs.tigera.io/archive/v3.22/networking/openstack/floating-ips https://docs.tigera.io/archive/v3.22/getting-started/ @@ -4412,7 +4412,7 @@ https://docs.tigera.io/archive/v3.19/reference/node/configuration https://docs.tigera.io/archive/v3.23/about/ https://docs.tigera.io/archive/v3.21/reference/architecture/design/l2-interconnect-fabric https://docs.tigera.io/archive/v3.17/networking/openstack/configuration -https://docs.tigera.io/archive/v3.17/reference/felix/pickle +https://docs.tigera.io/archive/v3.17/reference/felix/prometheus https://docs.tigera.io/archive/v3.12/getting-started/kubernetes/hardway/install-node https://docs.tigera.io/archive/v3.20/networking/openstack/configuration https://docs.tigera.io/archive/v3.19/reference/calicoctl/label @@ -4445,7 +4445,7 @@ https://docs.tigera.io/archive/v3.23/getting-started/kubernetes/k3s/multi-node-i https://docs.tigera.io/archive/v3.15/networking/workloads-outside-cluster https://docs.tigera.io/archive/v3.17/maintenance/troubleshoot/troubleshoot-ebpf https://docs.tigera.io/archive/v3.18/reference/host-endpoints/forwarded -https://docs.tigera.io/v3.9/maintenance/monitor/pickle +https://docs.tigera.io/v3.9/maintenance/monitor/prometheus https://docs.tigera.io/archive/v3.16/getting-started/clis/calicoctl/configure/overview https://docs.tigera.io/archive/v3.22/security/comms/crypto-auth https://docs.tigera.io/archive/v3.18/maintenance/ diff --git a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx index e567b9b1d2..b6eec1974f 100644 --- a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -310,7 +310,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -345,7 +345,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-cloud/reference/installation/_api.mdx b/calico-cloud/reference/installation/_api.mdx index 5b6d944a67..68757c8a13 100644 --- a/calico-cloud/reference/installation/_api.mdx +++ b/calico-cloud/reference/installation/_api.mdx @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx index f181f84411..a8c614a6e8 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -310,7 +310,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -345,7 +345,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx index 21483f65a4..0e9e1bbc58 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx index e567b9b1d2..b6eec1974f 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -310,7 +310,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -345,7 +345,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl_CE]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl_CE]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx index 5b6d944a67..68757c8a13 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx @@ -2512,7 +2512,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise/_includes/components/InstallAKS.js b/calico-enterprise/_includes/components/InstallAKS.js index f99e2da1c4..0a909b39e6 100644 --- a/calico-enterprise/_includes/components/InstallAKS.js +++ b/calico-enterprise/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise/_includes/components/InstallEKS.js b/calico-enterprise/_includes/components/InstallEKS.js index 6ee617a2f1..c971567072 100644 --- a/calico-enterprise/_includes/components/InstallEKS.js +++ b/calico-enterprise/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise/_includes/components/InstallGKE.js b/calico-enterprise/_includes/components/InstallGKE.js index 5539e101b4..11bfe1310b 100644 --- a/calico-enterprise/_includes/components/InstallGKE.js +++ b/calico-enterprise/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise/_includes/components/InstallGeneric.js b/calico-enterprise/_includes/components/InstallGeneric.js index 977f588d77..62e7c87125 100644 --- a/calico-enterprise/_includes/components/InstallGeneric.js +++ b/calico-enterprise/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js index fb017eb782..159d99bf39 100644 --- a/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js @@ -21,8 +21,8 @@ export default function OpenShiftPrometheusOperator(props) { BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} ); } diff --git a/calico-enterprise/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise/_includes/components/UpgradeOperatorSimple.js index 934b6b6487..561ec602c5 100644 --- a/calico-enterprise/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • diff --git a/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx index 73db0eeb15..5f2f05f16b 100644 --- a/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 10c59cd86d..fcd5931fc4 100644 --- a/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise/getting-started/install-on-clusters/rancher.mdx index 53c8fb1477..9209e9ad2a 100644 --- a/calico-enterprise/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise/getting-started/install-on-clusters/rke2.mdx index f53e85ef00..1555d904a6 100644 --- a/calico-enterprise/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 6ee8ea4480..9a386d7629 100644 --- a/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -60,7 +60,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -69,7 +69,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index eda9a700ce..7fde3dbbc7 100644 --- a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -91,7 +91,7 @@ The `tigera-operator` chart does not contain the $[prodname] CRDs, since Helm do ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -100,7 +100,7 @@ The `tigera-operator` chart does not contain the $[prodname] CRDs, since Helm do ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx index 909c846727..30402ed437 100644 --- a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx @@ -118,7 +118,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -159,7 +159,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -200,7 +200,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -241,7 +241,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -311,7 +311,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -346,7 +346,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -387,7 +387,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/operator-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/operator-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index 7a7051abee..fe355a5a4f 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -2188,7 +2188,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js index eeeb711465..d23b6ec54d 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallAKS.js @@ -31,7 +31,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -141,7 +141,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js index 41d89d0eec..afbd134d46 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallEKS.js @@ -33,7 +33,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -192,7 +192,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js index f9cb1a3604..89ebe93449 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGKE.js @@ -32,7 +32,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js index 7da879bf77..5d4ef1de9c 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/InstallGeneric.js @@ -37,7 +37,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js index fb017eb782..159d99bf39 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/OpenShiftPrometheusOperator.js @@ -21,8 +21,8 @@ export default function OpenShiftPrometheusOperator(props) { BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js index 81cfff6ba7..2af836a287 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.20-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx index ccf35e799b..c9b65e1bda 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -82,7 +82,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 50b9d4902f..c9ab5c70ed 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -102,7 +102,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx index 3174275da7..c4fa4047cf 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx @@ -70,7 +70,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx index 1b16aadabc..bc24244e1c 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx @@ -67,7 +67,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 5c0968d93b..e75e8d8562 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -37,7 +37,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index 331baed40f..8b80f0e7e9 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx index 8ccf536b6d..39c6d984ac 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -328,7 +328,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -363,7 +363,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx index a841978c30..46beb09a15 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx @@ -2408,7 +2408,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js index cdd1bcc48b..5fcb9cdb44 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js index afb6e89b33..825927ad3c 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js index 82478d4c9d..d08a015030 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js index 5d17b47c83..9b6180bee7 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js index fb017eb782..159d99bf39 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/OpenShiftPrometheusOperator.js @@ -21,8 +21,8 @@ export default function OpenShiftPrometheusOperator(props) { BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js index 81cfff6ba7..2af836a287 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.21-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx index dfbba79a40..16e959837c 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 6fa6c671a5..9ec8df81cc 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx index 1e2e4f3f9a..12d9dce3b2 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx index 0ee98fd119..c00c061dfa 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 62fc10299f..0e2df48ddb 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -47,7 +47,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index aba23727cc..9f80f6d50b 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx index f2331ebdc9..d8d46e5803 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -310,7 +310,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -345,7 +345,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx index 4bcc7309af..4e52c55293 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx @@ -2476,7 +2476,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js index cdd1bcc48b..5fcb9cdb44 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js index afb6e89b33..825927ad3c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js index 82478d4c9d..d08a015030 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js index 5d17b47c83..9b6180bee7 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js index fb017eb782..159d99bf39 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/OpenShiftPrometheusOperator.js @@ -21,8 +21,8 @@ export default function OpenShiftPrometheusOperator(props) { BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js index 934b6b6487..561ec602c5 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.22-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx index 51d9e5d148..c8f1627f6c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index c8ffd404ac..9cfa547111 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx index d3981c8913..f52b9dec88 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx index f0145b5b40..86e4afd16a 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index e13446b38c..a4b3cafcb7 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -47,7 +47,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index d15191df3b..f1f0e37869 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx index 3c276c8769..b6a11da77d 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -310,7 +310,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -345,7 +345,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx index 6bf96da4d3..599dd64d69 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx @@ -2513,7 +2513,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js index aa2835c186..e2ce3c2ee3 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js index 49e4512999..5486fe984f 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js index 1c4874586c..694a6c48e1 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js index 8bdb70713c..5266d4ca60 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js index fb017eb782..159d99bf39 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/OpenShiftPrometheusOperator.js @@ -21,8 +21,8 @@ export default function OpenShiftPrometheusOperator(props) { BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js index 934b6b6487..561ec602c5 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.23-2/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx index a11d6219d3..3d381e1f9a 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx index f0f640c771..8943823732 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx index d3981c8913..f52b9dec88 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx index f0145b5b40..86e4afd16a 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index e13446b38c..a4b3cafcb7 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -47,7 +47,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index d6c751104b..87c0e2b9e2 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -73,7 +73,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx index 3c276c8769..b6a11da77d 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -117,7 +117,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -158,7 +158,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -199,7 +199,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -240,7 +240,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -310,7 +310,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -345,7 +345,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx index c4dd15887e..336c5b990d 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx @@ -2514,7 +2514,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js index f99e2da1c4..0a909b39e6 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallAKS.js @@ -32,7 +32,7 @@ export default function InstallAKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -143,7 +143,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js index 6ee617a2f1..c971567072 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallEKS.js @@ -34,7 +34,7 @@ export default function InstallEKS(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    @@ -194,7 +194,7 @@ spec: If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js index 5539e101b4..11bfe1310b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGKE.js @@ -33,7 +33,7 @@ export default function InstallGKE(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml

  • Install your pull secret.

    diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js index 977f588d77..62e7c87125 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/InstallGeneric.js @@ -38,7 +38,7 @@ export default function InstallGeneric(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with {prodname}, your Prometheus operator must be v0.40.0 or higher. - kubectl create -f {filesUrl}/manifests/tigera-pickle-operator.yaml + kubectl create -f {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js index fb017eb782..159d99bf39 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/OpenShiftPrometheusOperator.js @@ -21,8 +21,8 @@ export default function OpenShiftPrometheusOperator(props) { BYO Prometheus that you manage yourself. {props.operation === 'install' - ? oc create -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml - : oc apply -f {filesUrl}/manifests/ocp/tigera-pickle-operator.yaml} + ? oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml + : oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml} ); } diff --git a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js index 934b6b6487..561ec602c5 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js +++ b/calico-enterprise_versioned_docs/version-3.24-1/_includes/components/UpgradeOperatorSimple.js @@ -40,7 +40,7 @@ export default function UpgradeOperatorSimple(props) { If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. - curl -L -O {filesUrl}/manifests/tigera-pickle-operator.yaml + curl -L -O {filesUrl}/manifests/tigera-prometheus-operator.yaml
  • diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx index 73db0eeb15..5f2f05f16b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/docker-enterprise.mdx @@ -83,7 +83,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx index 10c59cd86d..fcd5931fc4 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx @@ -103,7 +103,7 @@ A Linux host that meets the following requirements. ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx index 53c8fb1477..9209e9ad2a 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx @@ -71,7 +71,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx index f53e85ef00..1555d904a6 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx @@ -68,7 +68,7 @@ The geeky details of what you get: ::: ```bash - kubectl create -f $[filesUrl]/manifests/tigera-pickle-operator.yaml + kubectl create -f $[filesUrl]/manifests/tigera-prometheus-operator.yaml ``` 1. Install your pull secret. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx index 6ee8ea4480..9a386d7629 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx @@ -60,7 +60,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -69,7 +69,7 @@ The following steps assume the Calico deployment is installed on `tigera-operato ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl create -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl create -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl create -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx index 69b63788b1..f5ec8df6b3 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx @@ -86,7 +86,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v1_crd_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` @@ -95,7 +95,7 @@ These steps differ based on your cluster type. If you are unsure of your cluster ```bash kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/v3_projectcalico_org.yaml - kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f $[filesUrl]/manifests/eck-operator-crds.yaml ``` diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx index 909c846727..30402ed437 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx @@ -118,7 +118,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -159,7 +159,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -200,7 +200,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -241,7 +241,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -311,7 +311,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -346,7 +346,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -387,7 +387,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f $[filesUrl]/manifests/pickle/operator-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f $[filesUrl]/manifests/prometheus/operator-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx index 7957e821fe..482e318f8f 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx @@ -2204,7 +2204,7 @@ _Appears in:_ | `honorLabels` _boolean_ | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` _boolean_ | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` _RelabelConfig array_ | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | +| `relabelings` _RelabelConfig array_ | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config | ### EnvoySettings diff --git a/static/calico-cloud/llms-full.txt b/static/calico-cloud/llms-full.txt index c6780ff5a5..a6450c27d8 100644 --- a/static/calico-cloud/llms-full.txt +++ b/static/calico-cloud/llms-full.txt @@ -17176,7 +17176,7 @@ Your target application must be configured to receive data from the Calico Cloud - ``: the name of your Alertmanager service. - ``: the namespace associated with your Alertmanager service. If no namespace is specified in the Alertmanager service resource, then this value is `default`. - Alertmanager integration in Calico Cloud leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + Alertmanager integration in Calico Cloud leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). - **Generic JSON.** You must have a webhook URL for any other application you want the Calico Cloud webhook to send alerts to. @@ -24666,7 +24666,7 @@ In Calico Cloud, we program these LUTs to the eBPF data plane as maps which can ## Additional resources[​](#additional-resources) -- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle#load-balancer-metrics) +- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus#load-balancer-metrics) - [FelixConfiguration](https://docs.tigera.io/calico-cloud/reference/resources/felixconfig) - [Enable the eBPF data plane](https://docs.tigera.io/calico-cloud/operations/ebpf/enabling-ebpf) - [Advertise Service IPs with BGP](https://docs.tigera.io/calico-cloud/networking/configuring/advertise-service-ips) @@ -24715,7 +24715,7 @@ It is not possible to remove all backends of a service from backend selection vi - [Enable the eBPF data plane](https://docs.tigera.io/calico-cloud/operations/ebpf/enabling-ebpf) - [Maglev Load Balancing](https://docs.tigera.io/calico-cloud/networking/configuring/add-maglev-load-balancing) -- [Prometheus Metrics](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle#load-balancer-metrics) +- [Prometheus Metrics](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus#load-balancer-metrics) ### Egress gateways @@ -31084,25 +31084,25 @@ Post-installation tasks for managing Calico Cloud. ## Monitoring[​](#monitoring) -##### [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) +##### [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) -[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) +[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) ##### [Recommended Prometheus metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) [Recommended Prometheus metrics for Calico Cloud Typha, Felix, and policy components on connected clusters, covering the signals most critical to cluster health.](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) -##### [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) +##### [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) -[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) +[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) -##### [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) +##### [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) -[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) +[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) -##### [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) +##### [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) -[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) +[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) ##### [BGP metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/bgp-metrics) @@ -31474,9 +31474,9 @@ CSR names follow the pattern: `::`. -## [🗃Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) +## [🗃Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) -[5 items](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) +[5 items](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) ## [🗃Metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/) @@ -31486,31 +31486,31 @@ CSR names follow the pattern: `::`. -## [📄️Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) +## [📄️Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) -[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support) +[Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support) ## [📄️Recommended Prometheus metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) [Recommended Prometheus metrics for Calico Cloud Typha, Felix, and policy components on connected clusters, covering the signals most critical to cluster health.](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics) -## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) +## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) -[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) +[Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) -## [📄️Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) +## [📄️Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) -[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle) +[Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus) -## [📄️Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) +## [📄️Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) -[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager) +[Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager) ### Prometheus support ## Big picture[​](#big-picture) -Calico Cloud uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Cloud components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +Calico Cloud uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Cloud components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options[​](#install-options) @@ -31520,7 +31520,7 @@ Calico Cloud uses the open-source [Prometheus monitoring and alerting toolkit](h If you want to specify your own Prometheus operator during installation for management by the Tigera Operator, the require operator version must be **v0.40.0 or higher**. Because Calico Cloud creates Alertmanager and Prometheus CRs in the `tigera-pickle` namespace, all you need to do is verify that your Prometheus operator is configured to manage Prometheus and Alertmanager instances in the `tigera-pickle` namespace. -- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle) +- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus) ### Recommended Prometheus metrics @@ -32215,7 +32215,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32257,7 +32257,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32299,7 +32299,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -32341,7 +32341,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32368,7 +32368,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration). -For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle). +For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus). **For Windows nodes, create a service to expose Felix metrics** @@ -32425,7 +32425,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32459,7 +32459,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -32612,7 +32612,7 @@ spec: ## Creating a new alerting rule[​](#creating-a-new-alerting-rule) -Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) and [Queries](https://pickle.io/docs/querying/examples/) for more information. +Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node[​](#new-alerting-rule-for-monitoring-calico-node) @@ -32928,7 +32928,7 @@ The config-reloaders watch each pods file-system for updated config from ConfigM Alertmanager is used by Calico Cloud to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config[​](#updating-the-alertmanager-config) @@ -32958,7 +32958,7 @@ More detailed information about Alertmanager is available in the [upstream docum Your changes should be applied in a few seconds by the config-reloader container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). -For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules[​](#configure-inhibition-rules) @@ -33016,7 +33016,7 @@ receivers: - url: 'http://calico-alertmanager-webhook:30501/' ``` -More information, including descriptions of the various options can be found under the [route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. +More information, including descriptions of the various options can be found under the [route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. ### Metrics @@ -33138,7 +33138,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric[​](#bgp-peers-metric) @@ -33204,7 +33204,7 @@ irate(bgp_route_updates_received{ip_version="IPv4"}[5m]) ## Additional resources[​](#additional-resources) -- [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) +- [Configuring Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) ### Policy metrics @@ -33277,7 +33277,7 @@ Policy inspection and reporting is accomplished using four key pieces: Metrics will only be generated at a node when there are packets directed at an endpoint that are being actively profiled by a policy. Once generated they stay alive for 60 seconds. -Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/) for more information. +Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/) for more information. Because of metrics being expired, as just described, it is entirely possible for a GET on a metrics query URL to return no information. This is expected if there have not been any packets being processed by a policy on that node, in the last 60 seconds. @@ -34563,9 +34563,9 @@ APIs, CLI, architecture and design, and FAQ. [Reference for setting Kubernetes resource requests and limits on Calico Cloud components managed by the Tigera Operator in connected clusters.](https://docs.tigera.io/calico-cloud/reference/component-resources/configure-resources) -##### [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle) +##### [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus) -[Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth.](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle) +[Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth.](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus) ##### [Configuring cnx-node](https://docs.tigera.io/calico-cloud/reference/component-resources/node/configuration) @@ -34575,9 +34575,9 @@ APIs, CLI, architecture and design, and FAQ. [Reference for Felix configuration parameters in Calico Cloud connected clusters covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration) -##### [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) +##### [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) -[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) +[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) ## Configuration on public clouds[​](#configuration-on-public-clouds) @@ -36833,7 +36833,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | `honorLabels` *boolean* | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` *boolean* | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` *RelabelConfig array* | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: [https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel\_config](https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config) | +| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: [https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel\_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) | ### EnvoySettings[​](#envoysettings) @@ -50818,7 +50818,7 @@ This command will output the configured resource requests and limits for the Pac The `tigera/kube-controllers` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the Calico Cloud datastore. - To configure the controllers, see the [KubeControllersConfiguration](https://docs.tigera.io/calico-cloud/reference/resources/kubecontrollersconfig) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle). +- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus). ### Monitoring kube-controllers with Prometheus @@ -51181,9 +51181,9 @@ Setting CALICO\_ROUTER\_ID to value `hash` will use a hash of the configured nod [Reference for Felix configuration parameters in Calico Cloud connected clusters covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration) -## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) +## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) -[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle) +[Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus) ### Configuring Felix diff --git a/static/calico-cloud/llms.txt b/static/calico-cloud/llms.txt index f71f44933f..32467aadc7 100644 --- a/static/calico-cloud/llms.txt +++ b/static/calico-cloud/llms.txt @@ -227,12 +227,12 @@ - [Access usage data programmatically](https://docs.tigera.io/calico-cloud/operations/usage-api): Create a read-only API key in the Calico Cloud web console and use it to call the Usage API to retrieve vCPU usage data programmatically. - [Provide TLS certificates for Calico components](https://docs.tigera.io/calico-cloud/operations/comms/): Provide custom TLS certificates for Calico components. - [Monitoring](https://docs.tigera.io/calico-cloud/operations/monitor/): Reference index for monitoring Calico Cloud connected clusters with Prometheus metrics covering BGP, policy, log collection, and component health. -- [Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Cloud for component metrics, alerts, and persistent storage on connected clusters. -- [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/support): Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options. +- [Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Cloud for component metrics, alerts, and persistent storage on connected clusters. +- [Prometheus support](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/support): Reference for Prometheus support in Calico Cloud connected clusters covering the bundled operator-managed install and bring-your-own Prometheus deployment options. - [Recommended Prometheus metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/recommended-metrics): Recommended Prometheus metrics for Calico Cloud Typha, Felix, and policy components on connected clusters, covering the signals most critical to cluster health. -- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/byo-pickle): Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters. -- [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/configure-pickle): Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources. -- [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/pickle/alertmanager): Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. +- [Bring your own Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/byo-prometheus): Scrape Calico Cloud component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus on connected clusters. +- [Configure Prometheus](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/configure-prometheus): Configure Calico Cloud Prometheus rules for denied-packet alerts and persistent storage on connected clusters by editing PrometheusRule and StorageClass resources. +- [Configure Alertmanager](https://docs.tigera.io/calico-cloud/operations/monitor/prometheus/alertmanager): Configure Alertmanager in a Calico Cloud connected cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. - [Metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/): Reference index for Calico Cloud Prometheus metrics on connected clusters covering BGP, policy, log collection, and recommended dashboards. - [BGP metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/bgp-metrics): Monitor BGP peering and route exchange in Calico Cloud connected clusters by defining Prometheus rules and thresholds for peer health and route counts. - [Policy metrics](https://docs.tigera.io/calico-cloud/operations/monitor/metrics/policy-metrics): Monitor the runtime effect of policies on Calico Cloud connected clusters by defining Prometheus rules and thresholds that fire alerts on policy hits. @@ -297,12 +297,12 @@ - [Configuring the Calico Cloud CNI plugins](https://docs.tigera.io/calico-cloud/reference/component-resources/configuration): Reference for configuring the CNI plugin in Calico Cloud connected clusters covering operator-managed and manifest-mode CNI options. - [Configure resource requests and limits](https://docs.tigera.io/calico-cloud/reference/component-resources/configure-resources): Reference for setting Kubernetes resource requests and limits on Calico Cloud components managed by the Tigera Operator in connected clusters. - [kube-controllers](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/): kube-controllers is a set of Kubernetes controllers for Calico Cloud. -- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/pickle): Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth. +- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/kube-controllers/prometheus): Prometheus metrics reference for the kube-controllers component in Calico Cloud connected clusters covering reconcile latency and queue depth. - [Calico Cloud node (cnx-node)](https://docs.tigera.io/calico-cloud/reference/component-resources/node/): Reference content for the cnx-node component in Calico Cloud connected clusters covering Felix, BIRD, and the per-node agent configuration. - [Configuring cnx-node](https://docs.tigera.io/calico-cloud/reference/component-resources/node/configuration): Reference for configuring the cnx-node container in Calico Cloud connected clusters through environment variables that control Felix, BIRD, and confd. - [Felix](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/): Reference content for Felix in Calico Cloud connected clusters, the per-node daemon that programs routes and tiered policy rules into the Linux data plane. - [Configuring Felix](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/configuration): Reference for Felix configuration parameters in Calico Cloud connected clusters covering environment variables, FelixConfiguration fields, and per-node overrides. -- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/pickle): Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation. +- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-cloud/reference/component-resources/node/felix/prometheus): Prometheus metrics reference for Felix in Calico Cloud connected clusters covering counters and gauges exposed for data plane health and policy evaluation. - [Configuration on public clouds](https://docs.tigera.io/calico-cloud/reference/public-cloud/): Public cloud reference for Calico Cloud covering platform-specific networking notes for AWS, Azure, and GCE connected clusters. - [Amazon Web Services](https://docs.tigera.io/calico-cloud/reference/public-cloud/aws): Reference for connecting Calico Cloud clusters running on Amazon Web Services covering supported networking modes and AWS platform notes. - [Azure](https://docs.tigera.io/calico-cloud/reference/public-cloud/azure): Reference for connecting Calico Cloud clusters running on Microsoft Azure covering supported networking modes and Azure platform notes. diff --git a/static/calico-enterprise/llms-full.txt b/static/calico-enterprise/llms-full.txt index 37062e0d9a..f881bbe1b8 100644 --- a/static/calico-enterprise/llms-full.txt +++ b/static/calico-enterprise/llms-full.txt @@ -892,7 +892,7 @@ A Linux host that meets the following requirements. > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. Install your pull secret. @@ -1173,7 +1173,7 @@ The geeky details of what you get: > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -1794,12 +1794,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml ``` You can now monitor progress with the following command: @@ -2058,12 +2058,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml ``` You can now monitor progress with the following command: @@ -2281,12 +2281,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml ``` You can now monitor progress with the following command: @@ -2421,7 +2421,7 @@ Install Calico Enterprise on an AKS managed Kubernetes cluster. > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -2481,7 +2481,7 @@ Wait until the `apiserver` shows a status of `Available`, then proceed to > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. Install your pull secret. @@ -2831,7 +2831,7 @@ The geeky details of what you get: > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -3118,7 +3118,7 @@ The geeky details of what you get: > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 5. Install your pull secret. @@ -3421,7 +3421,7 @@ The geeky details of what you get: > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. Install your pull secret. @@ -3544,7 +3544,7 @@ The geeky details of what you get: > **SECONDARY:** If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. Install your pull secret. @@ -3821,7 +3821,7 @@ The geeky details of what you get: > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -5186,7 +5186,7 @@ To create a Charmed Kubernetes cluster without a CNI, you can customize your dep > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -9015,7 +9015,7 @@ Calico Enterprise creates a default-deny for the calico-system namespace. If you ```bash kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/operator-crds.yaml - kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle-operator-crds.yaml + kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus-operator-crds.yaml kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/eck-operator-crds.yaml ``` @@ -9151,7 +9151,7 @@ For Calico Enterprise, upgrading multi-cluster management setups must include up > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9319,7 +9319,7 @@ If the `active-namespace` is `tigera-operator-enterprise`, then the cluster was > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9576,12 +9576,12 @@ cp calico/* manifests/ > > > - > [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) + > [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) > > that you manage yourself. ```bash - oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml + oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml ``` 3. If your cluster is a management cluster, apply a [ManagementCluster](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#managementcluster) CR to your cluster. @@ -9765,7 +9765,7 @@ If you receive error indicating the custom resource definitions or resource type > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9815,7 +9815,7 @@ If you receive error indicating the custom resource definitions or resource type > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9883,7 +9883,7 @@ These upgrade instructions will upgrade your AKS clusters with Azure CNI and an > If you have an existing Prometheus operator in your cluster that you want to use, skip this step. To work with Calico Enterprise, your Prometheus operator must be v0.40.0 or higher. ```bash - curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + curl -L -O https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. If you previously [installed using a private registry](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry), you will need to [push the new images ](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#push-calico-enterprise-images-to-your-private-registry)and then [update the manifest](https://docs.tigera.io/calico-enterprise/latest/getting-started/install-on-clusters/private-registry/private-registry-regular#run-the-operator-using-images-from-your-private-registry) downloaded in the previous step. @@ -9986,7 +9986,7 @@ If you receive error indicating the custom resource definitions or resource type ```bash kubectl apply --server-side --force-conflicts -f https://downloads.tigera.io/ee/v3.23.1/manifests/operator-crds.yaml - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle-operator-crds.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus-operator-crds.yaml kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/eck-operator-crds.yaml ``` @@ -10154,12 +10154,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) > > that you manage yourself. ```bash -oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml +oc apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml ``` You can now monitor progress with the following command: @@ -15597,7 +15597,7 @@ In Calico Enterprise, we program these LUTs to the eBPF data plane as maps which ## Additional resources[​](#additional-resources) -- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle#load-balancer-metrics) +- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus#load-balancer-metrics) - [FelixConfiguration](https://docs.tigera.io/calico-enterprise/latest/reference/resources/felixconfig) - [Enable the eBPF data plane](https://docs.tigera.io/calico-enterprise/latest/operations/ebpf/enabling-ebpf) - [Advertise Service IPs with BGP](https://docs.tigera.io/calico-enterprise/latest/networking/configuring/advertise-service-ips) @@ -15646,7 +15646,7 @@ It is not possible to remove all backends of a service from backend selection vi - [Enable the eBPF data plane](https://docs.tigera.io/calico-enterprise/latest/operations/ebpf/enabling-ebpf) - [Maglev Load Balancing](https://docs.tigera.io/calico-enterprise/latest/networking/configuring/add-maglev-load-balancing) -- [Prometheus Metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle#load-balancer-metrics) +- [Prometheus Metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus#load-balancer-metrics) ### Calico Enterprise networking for KubeVirt @@ -35753,7 +35753,7 @@ Follow these steps in the cluster you intend to use as the managed cluster. > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -35953,7 +35953,7 @@ kubectl create clusterrolebinding mcm-user-admin --serviceaccount=default:mcm-us > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -36143,7 +36143,7 @@ kubectl create clusterrolebinding mcm-user-admin --serviceaccount=default:mcm-us > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -36271,7 +36271,7 @@ Before you get started, make sure you have downloaded and configured the > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. Install your pull secret. @@ -36477,7 +36477,7 @@ kubectl create clusterrolebinding mcm-user-admin --serviceaccount=default:mcm-us > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 3. Install your pull secret. @@ -36583,7 +36583,7 @@ Wait until the `apiserver` shows a status of `Available`, then proceed to the ne > , your Prometheus operator must be v0.40.0 or higher. ```text - kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-pickle-operator.yaml + kubectl create -f https://downloads.tigera.io/ee/v3.23.1/manifests/tigera-prometheus-operator.yaml ``` 4. Install your pull secret. @@ -36974,12 +36974,12 @@ Apply the Calico Enterprise manifests for the Prometheus operato > > > -> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +> [BYO Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) > > that you manage yourself. ```bash -oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-pickle-operator.yaml +oc create -f https://downloads.tigera.io/ee/v3.23.1/manifests/ocp/tigera-prometheus-operator.yaml ``` You can now monitor progress with the following command: @@ -38513,7 +38513,7 @@ The steps above assume that you are configuring both federated endpoint identity ##### Check remote cluster connection[​](#check-remote-cluster-connection) -You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle#metric-reference). +You can validate in a local cluster that Typha has synced to the remote cluster through the [Prometheus metrics for Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus#metric-reference). Alternatively, you can check the Typha logs for remote cluster connection status. Run the following command: @@ -39256,7 +39256,7 @@ Your target application must be configured to receive data from the Calico Enter - ``: the name of your Alertmanager service. - ``: the namespace associated with your Alertmanager service. If no namespace is specified in the Alertmanager service resource, then this value is `default`. - Alertmanager integration in Calico Enterprise leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://pickle.io/docs/alerting/latest/alerts_api/). + Alertmanager integration in Calico Enterprise leverages the API v2 exposed by the Alertmanager. For more information, see the [Alertmanager API documentation](https://prometheus.io/docs/alerting/latest/alerts_api/). - **Generic JSON.** You must have a webhook URL for any other application you want the Calico Enterprise webhook to send alerts to. @@ -42203,21 +42203,21 @@ See [Provide TLS certificates for Calico Enterprise components](https://docs.tig ## Monitoring[​](#monitoring) -##### [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +##### [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) -[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) -##### [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) +##### [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) -[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) +[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) -##### [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) +##### [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) -[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) +[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) -##### [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) +##### [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) -[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) +[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) ##### [Recommended Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/recommended-metrics) @@ -44628,21 +44628,21 @@ The Tigera Operator reports license condition in `tigerastatus`, including a war Calico Enterprise provides license metrics, such as the number of days until license expiration, through the **License Agent** component and Prometheus. For details on deploying the license agent and creating expiration alerts, see [License metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/license-agent). -To route license alerts, see [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager). +To route license alerts, see [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager). ## Additional resources[​](#additional-resources) - [LicenseKey resource](https://docs.tigera.io/calico-enterprise/latest/reference/resources/licensekey) -- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) -- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) +- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) +- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) ### Monitoring -## [🗃Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) +## [🗃Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) -[4 items](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) +[4 items](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) ## [🗃Metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/) @@ -44652,27 +44652,27 @@ To route license alerts, see [Configure Alertmanager](https://docs.tigera.io/cal -## [📄️Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +## [📄️Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) -[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support) +[Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support) -## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) +## [📄️Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) -[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle) +[Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus) -## [📄️Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) +## [📄️Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) -[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle) +[Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus) -## [📄️Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) +## [📄️Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) -[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) +[Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules.](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) ### Prometheus support ## Big picture[​](#big-picture) -Calico Enterprise uses the open-source [Prometheus monitoring and alerting toolkit](https://pickle.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Enterprise components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. +Calico Enterprise uses the open-source [Prometheus monitoring and alerting toolkit](https://prometheus.io/docs/introduction/overview/). With these tools, you can view time-series metrics from Calico Enterprise components in the Prometheus and Grafana interfaces, or scrape the metrics for a BYO Prometheus deployment. ## Install options[​](#install-options) @@ -44694,7 +44694,7 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec": {"window ### Bring your own Prometheus[​](#bring-your-own-pickle) -For details, see [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle). +For details, see [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus). ### Bring your own Prometheus @@ -44828,7 +44828,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/elasticsearch-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -44870,7 +44870,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/fluentd-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/fluentd-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -44912,7 +44912,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/calico-node-monitor-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/calico-node-monitor-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in $NAMESPACE. @@ -44954,7 +44954,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/kube-controller-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -44981,7 +44981,7 @@ felixconfiguration.projectcalico.org/default patched For all Felix configuration values, see [Felix configuration](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration). -For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle). +For all Prometheus Felix configuration values, see [Felix Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus). **For Windows nodes, create a service to expose Felix metrics** @@ -45038,7 +45038,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/felix-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/felix-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -45072,7 +45072,7 @@ export NAMESPACE= ``` ```bash -kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/pickle/typha-metrics-service-monitor.yaml -n $NAMESPACE +kubectl apply -f https://downloads.tigera.io/ee/v3.23.1/manifests/prometheus/typha-metrics-service-monitor.yaml -n $NAMESPACE ``` The .yamls have no namespace defined so when you apply `kubectl`, it is applied in the $NAMESPACE. @@ -45225,7 +45225,7 @@ spec: ## Creating a new alerting rule[​](#creating-a-new-alerting-rule) -Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://pickle.io/docs/pickle/latest/configuration/alerting_rules/) and [Queries](https://pickle.io/docs/querying/examples/) for more information. +Creating a new alerting rule is straightforward once you figure out what you want your rule to look for. Check [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) and [Queries](https://prometheus.io/docs/querying/examples/) for more information. ### New alerting rule for monitoring Calico node[​](#new-alerting-rule-for-monitoring-calico-node) @@ -45541,7 +45541,7 @@ The config-reloaders watch each pods file-system for updated config from ConfigM Alertmanager is used by Calico Enterprise to route alerts from Prometheus to the administrators. It handles routing, deduplicating, grouping, silencing and inhibition of alerts. -More detailed information about Alertmanager is available in the [upstream documentation](https://pickle.io/docs/alerting/latest/configuration). +More detailed information about Alertmanager is available in the [upstream documentation](https://prometheus.io/docs/alerting/latest/configuration). ### Updating the Alertmanager config[​](#updating-the-alertmanager-config) @@ -45571,7 +45571,7 @@ More detailed information about Alertmanager is available in the [upstream docum Your changes should be applied in a few seconds by the config-reloader container inside the alertmanager pod launched by the pickle-operator (usually named `alertmanager-`). -For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://pickle.io/docs/alerting/latest/configuration/) documentation. +For more advice on writing alertmanager configuration files, see the [alertmanager configuration](https://prometheus.io/docs/alerting/latest/configuration/) documentation. ### Configure Inhibition Rules[​](#configure-inhibition-rules) @@ -45629,7 +45629,7 @@ receivers: - url: 'http://calico-alertmanager-webhook:30501/' ``` -More information, including descriptions of the various options can be found under the [route section](https://pickle.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. +More information, including descriptions of the various options can be found under the [route section](https://prometheus.io/docs/alerting/latest/configuration/#route) of the Alertmanager Configuration guide. ### Metrics @@ -45755,7 +45755,7 @@ spec: ## Additional resources[​](#additional-resources) - [LicenseKey resource](https://docs.tigera.io/calico-enterprise/latest/reference/resources/licensekey) -- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager) +- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager) ### Recommended Prometheus metrics @@ -46422,7 +46422,7 @@ To access BGP metrics directly, you must use the TLS credentials: curl --cacert bundle.pem --key key.pem --cert cert.pem https://:9900/metrics ``` -Refer to [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. +Refer to [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) for information on how to create a new Alerting rule or updating the scraping interval for how often Prometheus collects the metrics. ### BGP peers metric[​](#bgp-peers-metric) @@ -46498,7 +46498,7 @@ kubectl patch felixConfiguration default --type merge --patch '{"spec":{"windows ## Additional resources[​](#additional-resources) -- [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) +- [Configuring Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) ### Policy metrics @@ -46571,7 +46571,7 @@ Policy inspection and reporting is accomplished using four key pieces: Metrics will only be generated at a node when there are packets directed at an endpoint that are being actively profiled by a policy. Once generated they stay alive for 60 seconds. -Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/) for more information. +Once Prometheus scrapes a node and collects policy metrics, it will be available at Prometheus until the metric is considered *stale*, i.e., Prometheus has not seen any updates to this metric for some time. This time is configurable. Refer to [Configuring Prometheus configuration](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/) for more information. Because of metrics being expired, as just described, it is entirely possible for a GET on a metrics query URL to return no information. This is expected if there have not been any packets being processed by a policy on that node, in the last 60 seconds. @@ -52245,7 +52245,7 @@ Endpoint contains a subset of relevant fields from the Prometheus Endpoint struc | `honorLabels` *boolean* | HonorLabels chooses the metric's labels on collisions with target labels. | | `honorTimestamps` *boolean* | HonorTimestamps controls whether Prometheus respects the timestamps present in scraped data. | | `metricRelabelings` *RelabelConfig array* | MetricRelabelConfigs to apply to samples before ingestion. | -| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_pickle_job_name` label. More info: [https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel\_config](https://pickle.io/docs/pickle/latest/configuration/configuration/#relabel_config) | +| `relabelings` *RelabelConfig array* | RelabelConfigs to apply to samples before scraping. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The original scrape job's name is available via the `__tmp_prometheus_job_name` label. More info: [https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel\_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) | ### EnvoySettings[​](#envoysettings) @@ -71013,7 +71013,7 @@ The Linseed API uses mTLS to connect to clients, and provides an API to access E ### Prometheus[​](#pickle) -**Main task**: The default monitoring component for collecting Calico Enterprise policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle), and [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/). +**Main task**: The default monitoring component for collecting Calico Enterprise policy metrics. It can also be used to collect metrics on calico/nodes from Felix. Prometheus is an open-source toolkit for systems monitoring and alerting. [Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus), and [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/). ## Calico open-source components[​](#calico-open-source-components-1) @@ -73548,7 +73548,7 @@ The [Monitor](https://docs.tigera.io/calico-enterprise/latest/reference/installa ### Prometheus[​](#pickle) -To configure resource specification for the [Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/installation/api#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' @@ -73883,7 +73883,7 @@ kubectl get deployment.apps/calico-apiserver -n calico-system -o json | jq '.spe The `tigera/kube-controllers` container runs a set of controllers that monitor the Kubernetes API and reconcile cluster state with the Calico Enterprise datastore. - To configure the controllers, see the [KubeControllersConfiguration](https://docs.tigera.io/calico-enterprise/latest/reference/resources/kubecontrollersconfig) resource reference. -- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/pickle). +- For exported Prometheus metrics, see [Prometheus statistics](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/prometheus). ### Monitoring kube-controllers with Prometheus @@ -74246,9 +74246,9 @@ Setting CALICO\_ROUTER\_ID to value `hash` will use a hash of the configured nod [Reference for Felix configuration parameters in Calico Enterprise covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration) -## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle) +## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus) -[Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle) +[Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus) ### Configuring Felix @@ -82634,9 +82634,9 @@ Can be 1 or 0 (true or false). Indicates whether Felix's node has been marked fo [Reference for Typha configuration parameters in Calico Enterprise covering environment variables and config file options for scaling the Kubernetes datastore.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/configuration) -## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle) +## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus) -[Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle) +[Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus) ### Reduce node impacts on datastore diff --git a/static/calico-enterprise/llms.txt b/static/calico-enterprise/llms.txt index 668b2543e1..2691478bdd 100644 --- a/static/calico-enterprise/llms.txt +++ b/static/calico-enterprise/llms.txt @@ -278,11 +278,11 @@ - [Advanced Node Scheduling](https://docs.tigera.io/calico-enterprise/latest/operations/logstorage/advanced-node-scheduling): Steer Calico Enterprise Elasticsearch pod and replica placement across Kubernetes nodes with data-node selectors and shard scheduling controls. - [License expiration and renewal](https://docs.tigera.io/calico-enterprise/latest/operations/license-options): Track Calico Enterprise license expiration through tigerastatus and license agent Prometheus metrics to keep observability and management features available. - [Monitoring](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/): Reference index for monitoring Calico Enterprise clusters with the bundled Prometheus stack covering BGP, policy, log storage, and operator metrics. -- [Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Enterprise for component metrics, alerts, and persistent storage. -- [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/support): Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options. -- [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/byo-pickle): Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus. -- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/configure-pickle): Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources. -- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/pickle/alertmanager): Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. +- [Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/): Configure the open-source Prometheus monitoring and alerting toolkit bundled with Calico Enterprise for component metrics, alerts, and persistent storage. +- [Prometheus support](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/support): Reference for Prometheus support in Calico Enterprise covering the bundled operator-managed install and bring-your-own Prometheus deployment options. +- [Bring your own Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/byo-prometheus): Scrape Calico Enterprise component metrics from an existing bring-your-own Prometheus deployment instead of the bundled operator-managed Prometheus. +- [Configure Prometheus](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/configure-prometheus): Configure Calico Enterprise Prometheus rules for denied-packet alerts and persistent storage by editing the bundled PrometheusRule and StorageClass resources. +- [Configure Alertmanager](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/prometheus/alertmanager): Configure Alertmanager in a Calico Enterprise cluster to route Prometheus alerts to operators with deduplication, grouping, silencing, and inhibition rules. - [Metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/): Reference index for Calico Enterprise Prometheus metrics covering BGP, policy, log storage, and recommended dashboards. - [License metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/license-agent): Monitor Calico Enterprise license metrics such as how many days until license expires. - [Recommended Prometheus metrics](https://docs.tigera.io/calico-enterprise/latest/operations/monitor/metrics/recommended-metrics): Recommended Prometheus metrics for Calico Enterprise Typha, Felix, and policy components, covering the signals most critical to cluster health. @@ -414,16 +414,16 @@ - [Configuring the Calico Enterprise CNI plugins](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/configuration): Reference for configuring the CNI plugin in Calico Enterprise covering operator-managed and manifest-mode CNI configuration options. - [Configure resource requests and limits](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/configure-resources): Reference for setting Kubernetes resource requests and limits on Calico Enterprise components managed by the Tigera Operator. - [kube-controllers](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/): Reference content for the kube-controllers component in Calico Enterprise that watches Kubernetes API events and reconciles cluster state. -- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/pickle): Prometheus metrics reference for the kube-controllers component in Calico Enterprise covering reconcile latency and queue depth. +- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/kube-controllers/prometheus): Prometheus metrics reference for the kube-controllers component in Calico Enterprise covering reconcile latency and queue depth. - [Calico Enterprise node (cnx-node)](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/): Reference content for the cnx-node component in Calico Enterprise covering Felix, BIRD, and the per-node agent configuration. - [Configuring cnx-node](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/configuration): Reference for configuring the cnx-node container in Calico Enterprise through environment variables that control Felix, BIRD, and confd. - [Felix](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/): Reference content for Felix in Calico Enterprise, the per-node daemon that programs routes and tiered policy rules into the Linux data plane. - [Configuring Felix](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/configuration): Reference for Felix configuration parameters in Calico Enterprise covering environment variables, FelixConfiguration fields, and per-node overrides. -- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/pickle): Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation. +- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/node/felix/prometheus): Prometheus metrics reference for Felix in Calico Enterprise covering counters and gauges exposed for data plane health and policy evaluation. - [Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/): Reference content for the Typha component in Calico Enterprise that scales Felix connections to the Kubernetes API datastore. - [Reduce node impacts on datastore](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/overview): Reference overview of the Typha daemon in Calico Enterprise explaining how it reduces datastore load and scales Felix to large clusters. - [Configuring Typha](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/configuration): Reference for Typha configuration parameters in Calico Enterprise covering environment variables and config file options for scaling the Kubernetes datastore. -- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/pickle): Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics. +- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico-enterprise/latest/reference/component-resources/typha/prometheus): Prometheus metrics reference for Typha in Calico Enterprise covering connection counts, cache health, and fan-out metrics. - [Configuration on public clouds](https://docs.tigera.io/calico-enterprise/latest/reference/public-cloud/): Public cloud reference for Calico Enterprise covering platform-specific networking notes for AWS, Azure, and GCE deployments. - [Amazon Web Services](https://docs.tigera.io/calico-enterprise/latest/reference/public-cloud/aws): Reference for running Calico Enterprise on Amazon Web Services covering supported networking modes and AWS platform integration notes. - [Azure](https://docs.tigera.io/calico-enterprise/latest/reference/public-cloud/azure): Reference for running Calico Enterprise on Microsoft Azure covering supported networking modes and user-defined routes. diff --git a/static/calico/3.25/licenses/third-party-attributions.html b/static/calico/3.25/licenses/third-party-attributions.html index 48ac14ed9c..50263db0a0 100644 --- a/static/calico/3.25/licenses/third-party-attributions.html +++ b/static/calico/3.25/licenses/third-party-attributions.html @@ -8760,7 +8760,7 @@

    Package Info

    - client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/pickle/client_golang + client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/prometheus/client_golang
    @@ -9214,7 +9214,7 @@

    Package Info

    - client_model (63fb9822ca3ba7a4ba5184071fb8f2ea000a99ef) git+github.com/pickle/client_model + client_model (63fb9822ca3ba7a4ba5184071fb8f2ea000a99ef) git+github.com/prometheus/client_model
    @@ -11272,7 +11272,7 @@

    Package Info

    - common (0ec6a33fff8b8a6950b82f03c4bfabaf61ac4813) git+github.com/pickle/common + common (0ec6a33fff8b8a6950b82f03c4bfabaf61ac4813) git+github.com/prometheus/common
    @@ -32883,8 +32883,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus
    @@ -58956,7 +58956,7 @@

    Package Info

    - procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/pickle/procfs + procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/prometheus/procfs
    diff --git a/static/calico/3.26/licenses/index.html b/static/calico/3.26/licenses/index.html index fc0fb2c70b..f06134159c 100644 --- a/static/calico/3.26/licenses/index.html +++ b/static/calico/3.26/licenses/index.html @@ -5290,7 +5290,7 @@

    Package Info

    - client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/pickle/client_golang + client_golang (254e5468413f19fb75cdad45f5ddc0b8c975188c) git+github.com/prometheus/client_golang
    @@ -5744,7 +5744,7 @@

    Package Info

    - client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/pickle/client_model + client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/prometheus/client_model
    @@ -7802,7 +7802,7 @@

    Package Info

    - common (49b36038aead362ce78f09337dc5872000bd048a) git+github.com/pickle/common + common (49b36038aead362ce78f09337dc5872000bd048a) git+github.com/prometheus/common
    @@ -29054,8 +29054,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus
    @@ -56700,7 +56700,7 @@

    Package Info

    - procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/pickle/procfs + procfs (344b47c663a30bfb28ca622d488a1cb6c29d6244) git+github.com/prometheus/procfs
    diff --git a/static/calico/3.27/licenses/third-party-attributions.html b/static/calico/3.27/licenses/third-party-attributions.html index 88836fc6ab..2498ec3038 100644 --- a/static/calico/3.27/licenses/third-party-attributions.html +++ b/static/calico/3.27/licenses/third-party-attributions.html @@ -11298,7 +11298,7 @@

    Package Info

    - client_golang (3583c1e1d085b75cab406c78b015562d45552b39) git+github.com/pickle/client_golang + client_golang (3583c1e1d085b75cab406c78b015562d45552b39) git+github.com/prometheus/client_golang
    @@ -11821,7 +11821,7 @@

    Package Info

    Authors: bwplotka@gmail.com, arthur.sens@coralogix.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, superq@gmail.com, 49699333+dependabot[bot]@users.noreply.github.com, arthursens2005@gmail.com, @@ -11972,7 +11972,7 @@

    Package Info

    seth.bunce@gmail.com, 86919550+lukasauk@users.noreply.github.com
    • -
  • Package Download URL: https://github.com/pickle/client_golang/archive/3583c1e1d085b75cab406c78b015562d45552b39.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_golang/archive/3583c1e1d085b75cab406c78b015562d45552b39.zip
  • File Path(s): go.mod
    • @@ -11980,7 +11980,7 @@

    Package Info

    - client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/pickle/client_model + client_model (91c3945f2cfbfb9040e34a0b6764d804b5a5a490) git+github.com/prometheus/client_model
    @@ -12431,7 +12431,7 @@

    Package Info

  • Authors: beorn@grafana.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, 49699333+dependabot[bot]@users.noreply.github.com, superq@gmail.com, zhaoziqi9146@gmail.com, @@ -12446,7 +12446,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com
    • -
  • Package Download URL: https://github.com/pickle/client_model/archive/91c3945f2cfbfb9040e34a0b6764d804b5a5a490.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_model/archive/91c3945f2cfbfb9040e34a0b6764d804b5a5a490.zip
  • File Path(s): go.mod
    • @@ -15121,7 +15121,7 @@

    Package Info

    - common (94bf9828e56d9670579b28a9f78237d3cd8d0395) git+github.com/pickle/common + common (94bf9828e56d9670579b28a9f78237d3cd8d0395) git+github.com/prometheus/common
    @@ -15683,7 +15683,7 @@

    Package Info

    dstdfx@gmail.com, abursavich@gmail.com, jbampton@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, pasquier.simon@gmail.com, cyril.tovena@gmail.com, bknecht@protonmail.ch, @@ -15756,7 +15756,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@pickle.io, + matthias@prometheus.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -15765,7 +15765,7 @@

    Package Info

    38865967+wasim-nihal@users.noreply.github.com, arianna.vespri@yahoo.it -
  • Package Download URL: https://github.com/pickle/common/archive/94bf9828e56d9670579b28a9f78237d3cd8d0395.zip
    • +
  • Package Download URL: https://github.com/prometheus/common/archive/94bf9828e56d9670579b28a9f78237d3cd8d0395.zip
  • File Path(s): go.mod
    • @@ -47235,8 +47235,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus
    @@ -47707,7 +47707,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -88763,7 +88763,7 @@

    Package Info

    - procfs (332e865adfebaa7eaedc94535a3f12f7e5eeb2d4) git+github.com/pickle/procfs + procfs (332e865adfebaa7eaedc94535a3f12f7e5eeb2d4) git+github.com/prometheus/procfs
    @@ -89225,7 +89225,7 @@

    Package Info

    superq@gmail.com, 49479987+bo-er@users.noreply.github.com, binjip978@gmail.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, benjamin.drung@ionos.com, sergii@zasenko.name, kulakov.home@gmail.com, @@ -89321,7 +89321,7 @@

    Package Info

    mdlayher@gmail.com, mwasilewski@gmx.com -
  • Package Download URL: https://github.com/pickle/procfs/archive/332e865adfebaa7eaedc94535a3f12f7e5eeb2d4.zip
    • +
  • Package Download URL: https://github.com/prometheus/procfs/archive/332e865adfebaa7eaedc94535a3f12f7e5eeb2d4.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.28/licenses/third-party-attributions.html b/static/calico/3.28/licenses/third-party-attributions.html index 869af50331..706f211d3c 100644 --- a/static/calico/3.28/licenses/third-party-attributions.html +++ b/static/calico/3.28/licenses/third-party-attributions.html @@ -12440,7 +12440,7 @@

    Package Info

    - client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/pickle/client_golang + client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/prometheus/client_golang
    @@ -12963,7 +12963,7 @@

    Package Info

    Authors: bwplotka@gmail.com, arthur.sens@coralogix.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, superq@gmail.com, 49699333+dependabot[bot]@users.noreply.github.com, arthursens2005@gmail.com, @@ -13114,7 +13114,7 @@

    Package Info

    krajorama@users.noreply.github.com, gyorgy.krajcsovits@grafana.com -
  • Package Download URL: https://github.com/pickle/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
  • File Path(s): go.mod
    • @@ -13122,7 +13122,7 @@

    Package Info

    - client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/pickle/client_model + client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/prometheus/client_model
    @@ -13574,7 +13574,7 @@

    Package Info

    Authors: beorn@grafana.com, 49699333+dependabot[bot]@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, superq@gmail.com, zhaoziqi9146@gmail.com, arianna.vespri@yahoo.it, @@ -13588,7 +13588,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com -
  • Package Download URL: https://github.com/pickle/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
  • File Path(s): go.mod
    • @@ -15031,7 +15031,7 @@

    Package Info

    - common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/pickle/common + common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/prometheus/common
    @@ -15590,7 +15590,7 @@

    Package Info

    superq@gmail.com, owen.williams@grafana.com, 49699333+dependabot[bot]@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, mail@jkroepke.de, 33664289+tjhop@users.noreply.github.com, matthieu.morel35@gmail.com, @@ -15669,7 +15669,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@pickle.io, + matthias@prometheus.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -15678,7 +15678,7 @@

    Package Info

    38865967+wasim-nihal@users.noreply.github.com, arianna.vespri@yahoo.it -
  • Package Download URL: https://github.com/pickle/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
    • +
  • Package Download URL: https://github.com/prometheus/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
  • File Path(s): go.mod
    • @@ -30912,8 +30912,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus
    @@ -31384,7 +31384,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -56950,7 +56950,7 @@

    Package Info

    - procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/pickle/procfs + procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/prometheus/procfs
    @@ -57412,7 +57412,7 @@

    Package Info

    superq@gmail.com, 49479987+bo-er@users.noreply.github.com, binjip978@gmail.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, benjamin.drung@ionos.com, sergii@zasenko.name, kulakov.home@gmail.com, @@ -57510,7 +57510,7 @@

    Package Info

    mwasilewski@gmx.com, mhutchinson@gmail.com -
  • Package Download URL: https://github.com/pickle/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
    • +
  • Package Download URL: https://github.com/prometheus/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.29/licenses/third-party-attributions.html b/static/calico/3.29/licenses/third-party-attributions.html index 0953a07169..6de8a6a601 100644 --- a/static/calico/3.29/licenses/third-party-attributions.html +++ b/static/calico/3.29/licenses/third-party-attributions.html @@ -12730,7 +12730,7 @@

    Package Info

    - client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/pickle/client_golang + client_golang (53be91d12107cb69053a8792d0a3a2a6124d59cf) git+github.com/prometheus/client_golang

    @@ -13259,7 +13259,7 @@

    Package Info

    kakkoyun@users.noreply.github.com, saswataminsta@yahoo.com, 44365948+mahendrapaipuri@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, arthursens2005@gmail.com, dongjiang1989@126.com, 115284013+Saumya40-codes@users.noreply.github.com, @@ -13421,7 +13421,7 @@

    Package Info

    seth.bunce@gmail.com, 86919550+lukasauk@users.noreply.github.com -
  • Package Download URL: https://github.com/pickle/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_golang/archive/53be91d12107cb69053a8792d0a3a2a6124d59cf.zip
  • File Path(s): go.mod
    • @@ -13429,7 +13429,7 @@

    Package Info

    - client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/pickle/client_model + client_model (d56cd794bca9543da8cc93e95432cd64d5f99635) git+github.com/prometheus/client_model

    @@ -13880,7 +13880,7 @@

    Package Info

  • Authors: beorn@grafana.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, 49699333+dependabot[bot]@users.noreply.github.com, superq@gmail.com, zhaoziqi9146@gmail.com, @@ -13894,7 +13894,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com
    • -
  • Package Download URL: https://github.com/pickle/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_model/archive/d56cd794bca9543da8cc93e95432cd64d5f99635.zip
  • File Path(s): go.mod
    • @@ -16082,7 +16082,7 @@

    Package Info

    - common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/pickle/common + common (773d5664eb8d228d2c6ba235b1af12fbf7ee9020) git+github.com/prometheus/common

    @@ -16639,7 +16639,7 @@

    Package Info

    harm@dds.nl, arve.knudsen@gmail.com, julius.hinze@grafana.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, 33664289+tjhop@users.noreply.github.com, 49699333+dependabot[bot]@users.noreply.github.com, bwplotka@gmail.com, @@ -16722,7 +16722,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@pickle.io, + matthias@prometheus.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -16734,7 +16734,7 @@

    Package Info

    t.hoplock@gmail.com, federico.torres@grafana.com -
  • Package Download URL: https://github.com/pickle/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
    • +
  • Package Download URL: https://github.com/prometheus/common/archive/773d5664eb8d228d2c6ba235b1af12fbf7ee9020.zip
  • File Path(s): go.mod
    • @@ -36467,8 +36467,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus

    @@ -36939,7 +36939,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -70485,7 +70485,7 @@

    Package Info

    - procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/pickle/procfs + procfs (ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa) git+github.com/prometheus/procfs

    @@ -70947,7 +70947,7 @@

    Package Info

    superq@gmail.com, 49479987+bo-er@users.noreply.github.com, binjip978@gmail.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, benjamin.drung@ionos.com, sergii@zasenko.name, kulakov.home@gmail.com, @@ -71053,7 +71053,7 @@

    Package Info

    mmichish@yahoo-corp.jp, weidong@uniontech.com -
  • Package Download URL: https://github.com/pickle/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
    • +
  • Package Download URL: https://github.com/prometheus/procfs/archive/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.30/licenses/third-party-attributions.html b/static/calico/3.30/licenses/third-party-attributions.html index 63ef031add..065f79d75e 100644 --- a/static/calico/3.30/licenses/third-party-attributions.html +++ b/static/calico/3.30/licenses/third-party-attributions.html @@ -15107,7 +15107,7 @@

    Package Info

    - client_golang (8a42da3e4bfdc7ea408fcd886064dffc4daffb22) git+github.com/pickle/client_golang + client_golang (8a42da3e4bfdc7ea408fcd886064dffc4daffb22) git+github.com/prometheus/client_golang

    @@ -15711,7 +15711,7 @@

    Package Info

    beorn@grafana.com, jacksontj.89@gmail.com, carlpett@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, bjoern@rabenste.in, kgeorgie@redhat.com, yaozengzeng@foxmail.com, @@ -15900,7 +15900,7 @@

    Package Info

    86919550+lukasauk@users.noreply.github.com, ganeshvern@gmail.com -
  • Package Download URL: https://github.com/pickle/client_golang/archive/8a42da3e4bfdc7ea408fcd886064dffc4daffb22.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_golang/archive/8a42da3e4bfdc7ea408fcd886064dffc4daffb22.zip
  • File Path(s): go.mod
    • @@ -15908,7 +15908,7 @@

    Package Info

    - client_model (571429e996ba2d9499e3dcb12926767ba953c0ef) git+github.com/pickle/client_model + client_model (571429e996ba2d9499e3dcb12926767ba953c0ef) git+github.com/prometheus/client_model

    @@ -16360,7 +16360,7 @@

    Package Info

    Authors: superq@gmail.com, beorn@grafana.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, zhaoziqi9146@gmail.com, matt.proud@gmail.com, 49699333+dependabot[bot]@users.noreply.github.com, @@ -16373,7 +16373,7 @@

    Package Info

    arianna.vespri@yahoo.it, arthur.sens@coralogix.com -
  • Package Download URL: https://github.com/pickle/client_model/archive/571429e996ba2d9499e3dcb12926767ba953c0ef.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_model/archive/571429e996ba2d9499e3dcb12926767ba953c0ef.zip
  • File Path(s): go.mod
    • @@ -19089,7 +19089,7 @@

    Package Info

    - common (cf3c56f7b7d09d67cb46592c5e930651fd2d296e) git+github.com/pickle/common + common (cf3c56f7b7d09d67cb46592c5e930651fd2d296e) git+github.com/prometheus/common

    @@ -19539,7 +19539,7 @@

    Package Info

    @@ -47506,8 +47506,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus

    @@ -47978,7 +47978,7 @@

    Package Info

    spasquie@redhat.com, p.versockas@gmail.com -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -87903,7 +87903,7 @@

    Package Info

    - procfs (51919fd4b9d0aaca69854ac81bdeda5f96dab366) git+github.com/pickle/procfs + procfs (51919fd4b9d0aaca69854ac81bdeda5f96dab366) git+github.com/prometheus/procfs

    @@ -88365,7 +88365,7 @@

    Package Info

    wolandr@gmail.com, tklauser@distanz.ch, github@frittentheke.de, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, daniel.swarbrick@gmail.com, zhsj@debian.org, binjip978@gmail.com, @@ -88485,7 +88485,7 @@

    Package Info

    remuso@gmail.com, miliacristian4@gmail.com -
  • Package Download URL: https://github.com/pickle/procfs/archive/51919fd4b9d0aaca69854ac81bdeda5f96dab366.zip
    • +
  • Package Download URL: https://github.com/prometheus/procfs/archive/51919fd4b9d0aaca69854ac81bdeda5f96dab366.zip
  • File Path(s): go.mod
    • diff --git a/static/calico/3.31/licenses/third-party-attributions.html b/static/calico/3.31/licenses/third-party-attributions.html index 83d5213c17..c5b56f599e 100644 --- a/static/calico/3.31/licenses/third-party-attributions.html +++ b/static/calico/3.31/licenses/third-party-attributions.html @@ -19197,7 +19197,7 @@

    Package Info

    - client_golang (e4b2208dd8cb6d1425f00250db842ec3c1e8749e) git+github.com/pickle/client_golang + client_golang (e4b2208dd8cb6d1425f00250db842ec3c1e8749e) git+github.com/prometheus/client_golang

    @@ -19806,7 +19806,7 @@

    Package Info

    kakkoyun@users.noreply.github.com, saswataminsta@yahoo.com, 44365948+mahendrapaipuri@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, arthursens2005@gmail.com, dongjiang1989@126.com, 115284013+Saumya40-codes@users.noreply.github.com, @@ -19969,7 +19969,7 @@

    Package Info

    seth.bunce@gmail.com, 86919550+lukasauk@users.noreply.github.com -
  • Package Download URL: https://github.com/pickle/client_golang/archive/e4b2208dd8cb6d1425f00250db842ec3c1e8749e.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_golang/archive/e4b2208dd8cb6d1425f00250db842ec3c1e8749e.zip
  • File Path(s): go.mod
    • @@ -19977,7 +19977,7 @@

    Package Info

    - client_model (eb136e513d419e0c31ad750922f0a6f7675c2dee) git+github.com/pickle/client_model + client_model (eb136e513d419e0c31ad750922f0a6f7675c2dee) git+github.com/prometheus/client_model

    @@ -20428,7 +20428,7 @@

    Package Info

  • Authors: beorn@grafana.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, 49699333+dependabot[bot]@users.noreply.github.com, superq@gmail.com, zhaoziqi9146@gmail.com, @@ -20442,7 +20442,7 @@

    Package Info

    bjoern@soundcloud.com, matt.proud@gmail.com
    • -
  • Package Download URL: https://github.com/pickle/client_model/archive/eb136e513d419e0c31ad750922f0a6f7675c2dee.zip
    • +
  • Package Download URL: https://github.com/prometheus/client_model/archive/eb136e513d419e0c31ad750922f0a6f7675c2dee.zip
  • File Path(s): go.mod
    • @@ -23013,7 +23013,7 @@

    Package Info

    - common (75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a) git+github.com/pickle/common + common (75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a) git+github.com/prometheus/common

    @@ -23484,7 +23484,7 @@

    Package Info

    harm@dds.nl, arve.knudsen@gmail.com, julius.hinze@grafana.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, 33664289+tjhop@users.noreply.github.com, 49699333+dependabot[bot]@users.noreply.github.com, bwplotka@gmail.com, @@ -23568,7 +23568,7 @@

    Package Info

    github@gone.nl, 48383032+inosato@users.noreply.github.com, gonsalves.clayton@yahoo.co.in, - matthias@pickle.io, + matthias@prometheus.io, callumstyan@gmail.com, ganeshvern@gmail.com, jeanette.tan@grafana.com, @@ -23580,7 +23580,7 @@

    Package Info

    t.hoplock@gmail.com, federico.torres@grafana.com -
  • Package Download URL: https://github.com/pickle/common/archive/75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a.zip
    • +
  • Package Download URL: https://github.com/prometheus/common/archive/75c3814dc66c571cc82cee2d3a6bf5f37ee73f1a.zip
  • File Path(s): go.mod
    • @@ -56476,8 +56476,8 @@

    Package Info

    -
    - go-grpc-pickle (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-pickle +
    + go-grpc-prometheus (c225b8c3b01faf2899099b768856a9e916e5087b) git+github.com/grpc-ecosystem/go-grpc-prometheus

    @@ -56948,7 +56948,7 @@

    Package Info

    dominik@honnef.co, rune.aune@symbiont.io -
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-pickle/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
    • +
  • Package Download URL: https://github.com/grpc-ecosystem/go-grpc-prometheus/archive/c225b8c3b01faf2899099b768856a9e916e5087b.zip
  • File Path(s): go.mod
    • @@ -97012,7 +97012,7 @@

    Package Info

    - procfs (61fe41207276bc95c4c391762e9ef137385e8a5d) git+github.com/pickle/procfs + procfs (61fe41207276bc95c4c391762e9ef137385e8a5d) git+github.com/prometheus/procfs

    @@ -97463,7 +97463,7 @@

    Package Info

  • Authors: 49699333+dependabot[bot]@users.noreply.github.com, - pickle-team@googlegroups.com, + prometheus-team@googlegroups.com, jj@asama.ai, superq@gmail.com, robbat2@orbis-terrarum.net, @@ -97580,15 +97580,15 @@

    Package Info

    mmichish@yahoo-corp.jp, weidong@uniontech.com
    • -
  • Package Download URL: https://github.com/pickle/procfs/archive/61fe41207276bc95c4c391762e9ef137385e8a5d.zip
    • +
  • Package Download URL: https://github.com/prometheus/procfs/archive/61fe41207276bc95c4c391762e9ef137385e8a5d.zip
  • File Path(s): go.mod
    • -
    - pickle-operator (4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b) git+github.com/pickle-operator/pickle-operator +
    + prometheus-operator (4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b) git+github.com/prometheus-operator/prometheus-operator

    @@ -98652,7 +98652,7 @@

    Package Info

    145814986+Whitea029@users.noreply.github.com, angelbarrerasanchez@gmail.com -
  • Package Download URL: https://github.com/pickle-operator/pickle-operator/archive/4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b.zip
    • +
  • Package Download URL: https://github.com/prometheus-operator/prometheus-operator/archive/4126d60d8a8ae99be866cdd0d15546a4d3e9fe8b.zip
  • File Path(s): go.mod
    • @@ -145506,37 +145506,37 @@ 
    Copyright © 2021,2023-2024 Tigera, Inc. All rights reserved.
    Copyright © 2016 Microsoft Corporation
    - 
    Copyright © The pickle-operator Authors
    + 
    Copyright © The prometheus-operator Authors
    - 
    Copyright © 2016 The pickle-operator Authors
    + 
    Copyright © 2016 The prometheus-operator Authors
    - 
    Copyright © 2021 The pickle-operator Authors
    + 
    Copyright © 2021 The prometheus-operator Authors
    - 
    Copyright ©  The pickle-operator Authors
    + 
    Copyright ©  The prometheus-operator Authors
    - 
    Copyright © 2024 The pickle-operator Authors
    + 
    Copyright © 2024 The prometheus-operator Authors
    - 
    Copyright © 2019 The pickle-operator Authors
    + 
    Copyright © 2019 The prometheus-operator Authors
    - 
    Copyright © 2020 The pickle-operator Authors
    + 
    Copyright © 2020 The prometheus-operator Authors
    - 
    Copyright © 2018 The pickle-operator Authors
    + 
    Copyright © 2018 The prometheus-operator Authors
    - 
    Copyright © 2017 The pickle-operator Authors
    + 
    Copyright © 2017 The prometheus-operator Authors
    - 
    Copyright © 2023 The pickle-operator Authors
    + 
    Copyright © 2023 The prometheus-operator Authors
    - 
    Copyright © 2022 The pickle-operator Authors
    + 
    Copyright © 2022 The prometheus-operator Authors
    Copyright © 2017 Unknwon
    diff --git a/static/calico/3.32/licenses/third-party-attributions.html b/static/calico/3.32/licenses/third-party-attributions.html index b4ee0c0d0b..d283f64141 100644 --- a/static/calico/3.32/licenses/third-party-attributions.html +++ b/static/calico/3.32/licenses/third-party-attributions.html @@ -44809,8 +44809,8 @@

    Package Info

    -
    - github.com/grpc-ecosystem/go-grpc-pickle (v1.2.0) go+github.com/grpc-ecosystem/go-grpc-pickle +
    + github.com/grpc-ecosystem/go-grpc-prometheus (v1.2.0) go+github.com/grpc-ecosystem/go-grpc-prometheus

    @@ -44939,7 +44939,7 @@

    Package Info

    bclermont, AlekSi -
  • Package Download URL: https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-pickle/@v/v1.2.0.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-prometheus/@v/v1.2.0.zip
  • File Path(s): go.mod
    • @@ -52653,8 +52653,8 @@

    Package Info

    -
    - github.com/pickle-operator/pickle-operator/pkg/apis/monitoring (v0.80.1) go+github.com/pickle-operator/pickle-operator/pkg/apis/monitoring +
    + github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring (v0.80.1) go+github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring

    @@ -52669,7 +52669,7 @@ 

    -    Copyright 2018 The pickle-operator Authors
+    Copyright 2018 The prometheus-operator Authors
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
@@ -53117,15 +53117,15 @@ 
    Package Info
    
                       apgapg, 
                       artpdr
                   
-                                
  • Package Download URL: https://proxy.golang.org/github.com/pickle-operator/pickle-operator/pkg/apis/monitoring/@v/v0.80.1.zip
    • 
+                                
  • Package Download URL: https://proxy.golang.org/github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring/@v/v0.80.1.zip
    • 
                                   
  • File Path(s): go.mod
    •
    -
    - github.com/pickle/client_golang (v1.23.2) go+github.com/pickle/client_golang +
    + github.com/prometheus/client_golang (v1.23.2) go+github.com/prometheus/client_golang
    @@ -53609,15 +53609,15 @@

    Package Info

    jeffwidman, jimmidyson -
  • Package Download URL: https://proxy.golang.org/github.com/pickle/client_golang/@v/v1.23.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/client_golang/@v/v1.23.2.zip
  • File Path(s): go.mod
    • -
    - github.com/pickle/client_model (v0.6.2) go+github.com/pickle/client_model +
    + github.com/prometheus/client_model (v0.6.2) go+github.com/prometheus/client_model

    @@ -53742,15 +53742,15 @@

    Package Info

    bufdev, juliusv -
  • Package Download URL: https://proxy.golang.org/github.com/pickle/client_model/@v/v0.6.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/client_model/@v/v0.6.2.zip
  • File Path(s): go.mod
    • -
    - github.com/pickle/common (v0.67.2) go+github.com/pickle/common +
    + github.com/prometheus/common (v0.67.2) go+github.com/prometheus/common

    @@ -53975,15 +53975,15 @@

    Package Info

    FUSAKLA, mattkanwisher -
  • Package Download URL: https://proxy.golang.org/github.com/pickle/common/@v/v0.67.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/common/@v/v0.67.2.zip
  • File Path(s): go.mod
    • -
    - github.com/pickle/procfs (v0.19.2) go+github.com/pickle/procfs +
    + github.com/prometheus/procfs (v0.19.2) go+github.com/prometheus/procfs

    @@ -54271,7 +54271,7 @@

    Package Info

    felixonmars, flixr -
  • Package Download URL: https://proxy.golang.org/github.com/pickle/procfs/@v/v0.19.2.zip
    • +
  • Package Download URL: https://proxy.golang.org/github.com/prometheus/procfs/@v/v0.19.2.zip
  • File Path(s): go.mod
    • @@ -111885,7 +111885,7 @@ 
    Copyright © 2014-2021 Docker Inc.
    Copyright © 2016-2017 The New York Times Company
    - 
    Copyright © 2018 The pickle-operator Authors
    + 
    Copyright © 2018 The prometheus-operator Authors
    Copyright © 2014 Steve Francia <spf@spf13.com>.
    diff --git a/static/calico/llms-full.txt b/static/calico/llms-full.txt index f2d0186d30..943c8d8dfd 100644 --- a/static/calico/llms-full.txt +++ b/static/calico/llms-full.txt @@ -20485,7 +20485,7 @@ In Calico, we program these LUTs to the eBPF data plane as maps which can grow u ## Additional resources[​](#additional-resources) -- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico/latest/reference/felix/pickle#load-balancer-metrics) +- [Prometheus Metrics for Maglev](https://docs.tigera.io/calico/latest/reference/felix/prometheus#load-balancer-metrics) - [FelixConfiguration](https://docs.tigera.io/calico/latest/reference/resources/felixconfig) - [Enable the eBPF data plane](https://docs.tigera.io/calico/latest/operations/ebpf/enabling-ebpf) - [Advertise Service IPs with BGP](https://docs.tigera.io/calico/latest/networking/configuring/advertise-service-ips) @@ -37206,7 +37206,7 @@ EOF We can configure Prometheus using a ConfigMap to persistently store the desired settings. -> **SECONDARY:** A comprehensive guide about configuration file can be [found at this link](https://pickle.io/docs/pickle/latest/configuration/configuration/). +> **SECONDARY:** A comprehensive guide about configuration file can be [found at this link](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). @@ -37493,7 +37493,7 @@ spec: - name: pickle-pod - image: prom/pickle + image: prom/prometheus resources: @@ -37550,7 +37550,7 @@ kubectl port-forward pod/pickle-pod 9090:9090 -n calico-monitoring Browse to [http://localhost:9090](http://localhost:9090) you should be able to see pickle dashboard. Type **felix\_active\_local\_endpoints** in the Expression input textbox then hit the execute button. Console table should be populated with all your nodes and quantity of endpoints in each of them. -> **SECONDARY:** A list of Felix metrics can be [found at this link](https://docs.tigera.io/calico/latest/reference/felix/pickle). Similar lists can be found for [kube-controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle) and [Typha](https://docs.tigera.io/calico/latest/reference/typha/pickle). +> **SECONDARY:** A list of Felix metrics can be [found at this link](https://docs.tigera.io/calico/latest/reference/felix/prometheus). Similar lists can be found for [kube-controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus) and [Typha](https://docs.tigera.io/calico/latest/reference/typha/prometheus). Push the `Add Graph` button, You should be able to see the metric plotted on a Graph. @@ -39732,9 +39732,9 @@ APIs, CLI, architecture and design, and FAQ. [Reference for Felix configuration parameters in Calico Open Source covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico/latest/reference/felix/configuration) -##### [Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/pickle) +##### [Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/prometheus) -[Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico/latest/reference/felix/pickle) +[Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico/latest/reference/felix/prometheus) ## Typha[​](#typha) @@ -39746,9 +39746,9 @@ APIs, CLI, architecture and design, and FAQ. [Reference for Typha configuration parameters in Calico Open Source covering environment variables and config file options for scaling the Kubernetes datastore.](https://docs.tigera.io/calico/latest/reference/typha/configuration) -##### [Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/pickle) +##### [Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/prometheus) -[Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico/latest/reference/typha/pickle) +[Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico/latest/reference/typha/prometheus) ## Configuration on public clouds[​](#configuration-on-public-clouds) @@ -53445,9 +53445,9 @@ kubectl get deployment.apps/calico-apiserver -n calico-system -o json | jq '.spe [Reference for Felix configuration parameters in Calico Open Source covering environment variables, FelixConfiguration fields, and per-node overrides.](https://docs.tigera.io/calico/latest/reference/felix/configuration) -## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/pickle) +## [📄️Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/prometheus) -[Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico/latest/reference/felix/pickle) +[Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation.](https://docs.tigera.io/calico/latest/reference/felix/prometheus) ### Configuring Felix @@ -58500,9 +58500,9 @@ Total number of Maglev entries in conntrack table broken down by IP version, and [Reference for Typha configuration parameters in Calico Open Source covering environment variables and config file options for scaling the Kubernetes datastore.](https://docs.tigera.io/calico/latest/reference/typha/configuration) -## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/pickle) +## [📄️Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/prometheus) -[Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico/latest/reference/typha/pickle) +[Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics.](https://docs.tigera.io/calico/latest/reference/typha/prometheus) ### Typha overview @@ -59465,9 +59465,9 @@ For example: [Reference for kube-controllers configuration in Calico Open Source covering environment variables and KubeControllersConfiguration options.](https://docs.tigera.io/calico/latest/reference/kube-controllers/configuration) -## [📄️Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle) +## [📄️Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus) -[Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth.](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle) +[Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth.](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus) ### Configuring the Calico Kubernetes controllers diff --git a/static/calico/llms.txt b/static/calico/llms.txt index 19a3e96078..403d5b41c5 100644 --- a/static/calico/llms.txt +++ b/static/calico/llms.txt @@ -319,15 +319,15 @@ - [Configure resource requests and limits](https://docs.tigera.io/calico/latest/reference/configure-resources): Reference for setting Kubernetes resource requests and limits on Calico Open Source components managed by the Tigera Operator. - [Felix](https://docs.tigera.io/calico/latest/reference/felix/): Reference content for Felix in Calico Open Source, the per-node daemon that programs routes and policy rules into the Linux data plane. - [Configuring Felix](https://docs.tigera.io/calico/latest/reference/felix/configuration): Reference for Felix configuration parameters in Calico Open Source covering environment variables, FelixConfiguration fields, and per-node overrides. -- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/pickle): Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation. +- [Monitoring Felix with Prometheus](https://docs.tigera.io/calico/latest/reference/felix/prometheus): Prometheus metrics reference for Felix in Calico Open Source covering counters and gauges exposed for data plane health and policy evaluation. - [Typha](https://docs.tigera.io/calico/latest/reference/typha/): Reference content for Typha in Calico Open Source, the fan-out daemon that scales Felix connections to the Kubernetes API datastore. - [Typha overview](https://docs.tigera.io/calico/latest/reference/typha/overview): Reference overview of the Typha daemon in Calico Open Source explaining how it reduces datastore load and scales Felix to large clusters. - [Configuring Typha](https://docs.tigera.io/calico/latest/reference/typha/configuration): Reference for Typha configuration parameters in Calico Open Source covering environment variables and config file options for scaling the Kubernetes datastore. -- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/pickle): Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics. +- [Monitoring Typha with Prometheus](https://docs.tigera.io/calico/latest/reference/typha/prometheus): Prometheus metrics reference for Typha in Calico Open Source covering connection counts, cache health, and fan-out metrics. - [Configure the Calico CNI plugins](https://docs.tigera.io/calico/latest/reference/configure-cni-plugins): Reference for configuring the Calico Open Source CNI plugin and IPAM plugin through CNI network configuration files. - [kube-controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/): Reference content for the kube-controllers component in Calico Open Source that watches Kubernetes API events and reconciles cluster state. - [Configuring the Calico Kubernetes controllers](https://docs.tigera.io/calico/latest/reference/kube-controllers/configuration): Reference for kube-controllers configuration in Calico Open Source covering environment variables and KubeControllersConfiguration options. -- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/pickle): Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth. +- [Monitoring kube-controllers with Prometheus](https://docs.tigera.io/calico/latest/reference/kube-controllers/prometheus): Prometheus metrics reference for the kube-controllers component in Calico Open Source covering reconcile latency and queue depth. - [Configuration on public clouds](https://docs.tigera.io/calico/latest/reference/public-cloud/): Public cloud reference for Calico Open Source covering platform-specific networking notes for AWS, Azure, GCE, and IBM Cloud deployments. - [Amazon Web Services](https://docs.tigera.io/calico/latest/reference/public-cloud/aws): Reference for running Calico Open Source on Amazon Web Services covering supported networking modes, source/destination check requirements, and AWS-specific notes. - [Azure](https://docs.tigera.io/calico/latest/reference/public-cloud/azure): Reference for running Calico Open Source on Microsoft Azure covering supported networking modes, user-defined routes, and Azure platform notes. From 2034123115f7222b8c276dcbcf863558bf9f7f62 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 19 Aug 2026 17:35:52 +0000 Subject: [PATCH 6/6] Fix Copilot-flagged issues from blind prometheus->pickle rename - Grafana datasource "type" must remain the literal plugin identifier "prometheus" (calico monitor-component-visual.mdx, current + 3.29-3.32) - kubectl example resource name "picklerule" reverted to "prometheusrule" to match the unchanged `kind: PrometheusRule` CRD (configure-prometheus.mdx, license-options.mdx, operator-metrics.mdx, and versioned copies) - Broken #...pickle... anchor links reverted to match their unchanged target heading slugs (byo-prometheus.mdx, architecture overview.mdx, configure-resources.mdx, elasticsearch-and-fluentd-metrics.mdx, license-agent.mdx, and installation _api.mdx reference tables) Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_012uBgAMf3CkcrULiQQMJBTx --- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- calico-cloud/reference/installation/_api.mdx | 18 ++++++++--------- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/installation/_api.mdx | 18 ++++++++--------- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/installation/_api.mdx | 18 ++++++++--------- .../operations/license-options.mdx | 2 +- .../elasticsearch-and-fluentd-metrics.mdx | 4 ++-- .../monitor/metrics/operator-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/architecture/overview.mdx | 4 ++-- .../configure-resources.mdx | 2 +- .../reference/installation/_api.mdx | 20 +++++++++---------- .../elasticsearch-and-fluentd-metrics.mdx | 4 ++-- .../monitor/metrics/license-agent.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/architecture/overview.mdx | 4 ++-- .../configure-resources.mdx | 2 +- .../reference/installation/_api.mdx | 18 ++++++++--------- .../elasticsearch-and-fluentd-metrics.mdx | 4 ++-- .../monitor/metrics/license-agent.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/architecture/overview.mdx | 4 ++-- .../configure-resources.mdx | 2 +- .../reference/installation/_api.mdx | 18 ++++++++--------- .../elasticsearch-and-fluentd-metrics.mdx | 4 ++-- .../monitor/metrics/license-agent.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/architecture/overview.mdx | 4 ++-- .../configure-resources.mdx | 2 +- .../reference/installation/_api.mdx | 18 ++++++++--------- .../elasticsearch-and-fluentd-metrics.mdx | 4 ++-- .../monitor/metrics/license-agent.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/architecture/overview.mdx | 4 ++-- .../configure-resources.mdx | 2 +- .../reference/installation/_api.mdx | 18 ++++++++--------- .../operations/license-options.mdx | 2 +- .../elasticsearch-and-fluentd-metrics.mdx | 4 ++-- .../monitor/metrics/operator-metrics.mdx | 2 +- .../monitor/prometheus/byo-prometheus.mdx | 4 ++-- .../prometheus/configure-prometheus.mdx | 2 +- .../reference/architecture/overview.mdx | 4 ++-- .../configure-resources.mdx | 2 +- .../reference/installation/_api.mdx | 20 +++++++++---------- .../monitor/monitor-component-visual.mdx | 2 +- .../monitor/monitor-component-visual.mdx | 2 +- .../monitor/monitor-component-visual.mdx | 2 +- .../monitor/monitor-component-visual.mdx | 2 +- .../monitor/monitor-component-visual.mdx | 2 +- 58 files changed, 153 insertions(+), 153 deletions(-) diff --git a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx index b6eec1974f..513bc024ac 100644 --- a/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx index e0016226c3..8bcdf0aa7c 100644 --- a/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-cloud/reference/installation/_api.mdx b/calico-cloud/reference/installation/_api.mdx index 68757c8a13..24f3953b4e 100644 --- a/calico-cloud/reference/installation/_api.mdx +++ b/calico-cloud/reference/installation/_api.mdx @@ -1120,11 +1120,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4635,8 +4635,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5207,7 +5207,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5217,7 +5217,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5232,11 +5232,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5361,7 +5361,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx index a8c614a6e8..b183756e03 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx index 842742a6ea..d5dda4e561 100644 --- a/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-22-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx index 0e9e1bbc58..b94e7ab768 100644 --- a/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-22-2/reference/installation/_api.mdx @@ -1120,11 +1120,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4635,8 +4635,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5207,7 +5207,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5217,7 +5217,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5232,11 +5232,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5361,7 +5361,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx index b6eec1974f..513bc024ac 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx index e0016226c3..8bcdf0aa7c 100644 --- a/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-cloud_versioned_docs/version-23-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx index 68757c8a13..24f3953b4e 100644 --- a/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx +++ b/calico-cloud_versioned_docs/version-23-2/reference/installation/_api.mdx @@ -1120,11 +1120,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4635,8 +4635,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5207,7 +5207,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5217,7 +5217,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5232,11 +5232,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5361,7 +5361,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-enterprise/operations/license-options.mdx b/calico-enterprise/operations/license-options.mdx index e8148ca588..6c62e08c54 100644 --- a/calico-enterprise/operations/license-options.mdx +++ b/calico-enterprise/operations/license-options.mdx @@ -73,7 +73,7 @@ These metrics are scraped by the built-in Prometheus instance via the `tigera-op $[prodname] installs PrometheusRule resources with alerting rules for license expiration. You can view them with: ```bash -kubectl -n tigera-pickle get picklerule calico -o yaml +kubectl -n tigera-pickle get prometheusrule calico -o yaml ``` The built-in rules include: diff --git a/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 1c2be4cb28..6c52209d5d 100644 --- a/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch diff --git a/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx b/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx index 89b16ce55b..e084498a8c 100644 --- a/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx +++ b/calico-enterprise/operations/monitor/metrics/operator-metrics.mdx @@ -107,7 +107,7 @@ The `tigera_operator_tls_certificate_expiry_timestamp_seconds` metric reports th $[prodname] installs a PrometheusRule resource named `calico` with alerting rules that use these metrics. You can view it with: ```bash -kubectl -n tigera-pickle get picklerule calico -o yaml +kubectl -n tigera-pickle get prometheusrule calico -o yaml ``` The built-in rules include: diff --git a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx index 30402ed437..9650e4ad11 100644 --- a/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/byo-prometheus.mdx @@ -33,7 +33,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -75,7 +75,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx index adad191920..5d368edda4 100644 --- a/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-enterprise/reference/architecture/overview.mdx b/calico-enterprise/reference/architecture/overview.mdx index 4aca9a3587..3da4e4cd8b 100644 --- a/calico-enterprise/reference/architecture/overview.mdx +++ b/calico-enterprise/reference/architecture/overview.mdx @@ -29,13 +29,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#pickle-api-service) +- [Prometheus API service](#prometheus-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#pickle) +- [Prometheus](#prometheus) ## Calico open-source components diff --git a/calico-enterprise/reference/component-resources/configure-resources.mdx b/calico-enterprise/reference/component-resources/configure-resources.mdx index afaedd8ab0..93e8b5bbe3 100644 --- a/calico-enterprise/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise/reference/component-resources/configure-resources.mdx @@ -910,7 +910,7 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' diff --git a/calico-enterprise/reference/installation/_api.mdx b/calico-enterprise/reference/installation/_api.mdx index fe355a5a4f..8350bd0b87 100644 --- a/calico-enterprise/reference/installation/_api.mdx +++ b/calico-enterprise/reference/installation/_api.mdx @@ -1251,11 +1251,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4530,8 +4530,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertmanager` _[Alertmanager](#alertmanager)_ | (Optional) Alertmanager is the configuration for the Alertmanager. | @@ -5184,7 +5184,7 @@ _Appears in:_ - [ManagerDeploymentContainer](#managerdeploymentcontainer) - [PacketCaptureAPIDeploymentContainer](#packetcaptureapideploymentcontainer) - [PolicyRecommendationDeploymentContainer](#policyrecommendationdeploymentcontainer) -- [PrometheusContainer](#picklecontainer) +- [PrometheusContainer](#prometheuscontainer) - [TyphaDeploymentContainer](#typhadeploymentcontainer) - [WhiskerDeploymentContainer](#whiskerdeploymentcontainer) @@ -5222,7 +5222,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5232,7 +5232,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5249,11 +5249,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5378,7 +5378,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 5dd1ca8f77..c0344e8528 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx index bce3946549..8ea6e22cab 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/license-agent.mdx @@ -33,7 +33,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) ### Add license agent in your Kubernetes cluster diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx index 39c6d984ac..f607626733 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx index e805423e3c..28017dbf03 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx index 30b5d02f77..81c740d0f3 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#pickle-api-service) +- [Prometheus API service](#prometheus-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#pickle) +- [Prometheus](#prometheus) ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx index ca9384f07f..17b2f81140 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/configure-resources.mdx @@ -910,7 +910,7 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' diff --git a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx index 46beb09a15..8d3ef67769 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx @@ -1016,11 +1016,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -3857,8 +3857,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -4397,7 +4397,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -4407,7 +4407,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -4422,11 +4422,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -4520,7 +4520,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 5dd1ca8f77..c0344e8528 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx index 71afbc6a2f..54053c3a99 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/metrics/license-agent.mdx @@ -33,7 +33,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) ### Add license agent in your Kubernetes cluster diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx index d8d46e5803..88f95bd819 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx index e805423e3c..28017dbf03 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx index da874f5d26..329cfdf22e 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#pickle-api-service) +- [Prometheus API service](#prometheus-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#pickle) +- [Prometheus](#prometheus) ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx index 2629bf481d..81cda55fd5 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/configure-resources.mdx @@ -910,7 +910,7 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' diff --git a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx index 4e52c55293..b669aa0101 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/reference/installation/_api.mdx @@ -1084,11 +1084,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4470,8 +4470,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5026,7 +5026,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5036,7 +5036,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5051,11 +5051,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5179,7 +5179,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 1c2be4cb28..6c52209d5d 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx index c257b61323..d455745503 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/metrics/license-agent.mdx @@ -33,7 +33,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) ### Add license agent in your Kubernetes cluster diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx index b6a11da77d..41a5d3eda6 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx index a3471e9857..ffff72fa2a 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx index 52f6380007..2d6f3f4e96 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#pickle-api-service) +- [Prometheus API service](#prometheus-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#pickle) +- [Prometheus](#prometheus) ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx index 98393bb18e..0e51db4b10 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/configure-resources.mdx @@ -910,7 +910,7 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' diff --git a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx index 599dd64d69..d94aa7b37c 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/reference/installation/_api.mdx @@ -1121,11 +1121,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4800,8 +4800,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5372,7 +5372,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5382,7 +5382,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5397,11 +5397,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5526,7 +5526,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 1c2be4cb28..6c52209d5d 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx index 7b1dbb7379..dda16511cb 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/metrics/license-agent.mdx @@ -27,7 +27,7 @@ The **License Agent** is a containerized application that monitors the following ## How to - [Add license agent in your Kubernetes cluster](#add-license-agent-in-your-kubernetes-cluster) -- [Create alerts using Prometheus metrics](#create-alerts-using-pickle-metrics) +- [Create alerts using Prometheus metrics](#create-alerts-using-prometheus-metrics) ### Add license agent in your Kubernetes cluster diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx index b6a11da77d..41a5d3eda6 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/byo-prometheus.mdx @@ -32,7 +32,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -74,7 +74,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx index adad191920..5d368edda4 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx index 413d41a492..760400063c 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx @@ -30,13 +30,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#pickle-api-service) +- [Prometheus API service](#prometheus-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#pickle) +- [Prometheus](#prometheus) ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx index 5ffd6cfa40..47e5d558de 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/configure-resources.mdx @@ -910,7 +910,7 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' diff --git a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx index 336c5b990d..443f745abc 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/reference/installation/_api.mdx @@ -1121,11 +1121,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4801,8 +4801,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[AlertManager](#alertmanager)_ | (Optional) AlertManager is the configuration for the AlertManager. | @@ -5373,7 +5373,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5383,7 +5383,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5398,11 +5398,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5527,7 +5527,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx index e8148ca588..6c62e08c54 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx @@ -73,7 +73,7 @@ These metrics are scraped by the built-in Prometheus instance via the `tigera-op $[prodname] installs PrometheusRule resources with alerting rules for license expiration. You can view them with: ```bash -kubectl -n tigera-pickle get picklerule calico -o yaml +kubectl -n tigera-pickle get prometheusrule calico -o yaml ``` The built-in rules include: diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx index 1c2be4cb28..6c52209d5d 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/elasticsearch-and-fluentd-metrics.mdx @@ -24,8 +24,8 @@ Platform engineering teams rely on logs, such as flow logs and DNS logs, for vis ## How to -- [Create Prometheus alerts for Elasticsearch](#create-pickle-alerts-for-elasticsearch) -- [Create Prometheus alerts for Fluentd](#create-pickle-alerts-for-elasticsearch) +- [Create Prometheus alerts for Elasticsearch](#create-prometheus-alerts-for-elasticsearch) +- [Create Prometheus alerts for Fluentd](#create-prometheus-alerts-for-elasticsearch) ### Create Prometheus alerts for Elasticsearch diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx index 89b16ce55b..e084498a8c 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/metrics/operator-metrics.mdx @@ -107,7 +107,7 @@ The `tigera_operator_tls_certificate_expiry_timestamp_seconds` metric reports th $[prodname] installs a PrometheusRule resource named `calico` with alerting rules that use these metrics. You can view it with: ```bash -kubectl -n tigera-pickle get picklerule calico -o yaml +kubectl -n tigera-pickle get prometheusrule calico -o yaml ``` The built-in rules include: diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx index 30402ed437..9650e4ad11 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/byo-prometheus.mdx @@ -33,7 +33,7 @@ For the supported version of Prometheus in this release, see the [Release Notes] - [Scrape all enabled metrics](#scrape-all-enabled-metrics) - [Scrape metrics from specific components directly](#scrape-metrics-from-specific-components-directly) -- [Verify BYO Prometheus](#verify-byo-pickle) +- [Verify BYO Prometheus](#verify-byo-prometheus) - [Create policy to secure traffic between pods](#create-policy-to-secure-traffic-between-pods) - [Troubleshooting](#troubleshooting) @@ -75,7 +75,7 @@ The following example shows a Prometheus server installed in namespace "external kubectl get clusterrole tigera-external-pickle kubectl get clusterrolebinding tigera-external-pickle ``` - That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-pickle). + That's it. You should be seeing the new metrics show up in your Prometheus instance within a minute. For more information on verifying metrics, see the section, [Verify BYO Prometheus](#verify-byo-prometheus). ### Scrape metrics from specific components directly diff --git a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx index adad191920..5d368edda4 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/operations/monitor/prometheus/configure-prometheus.mdx @@ -12,7 +12,7 @@ The process of updating rules is the same as for user created rules (documented - Save the current alert rule: ```bash - kubectl -n tigera-pickle get picklerule -o yaml > calico-pickle-alert-rule-dp.yaml + kubectl -n tigera-pickle get prometheusrule -o yaml > calico-pickle-alert-rule-dp.yaml ``` - Make necessary edits to the alerting rules then apply the updated manifest. diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx index 4aca9a3587..3da4e4cd8b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx @@ -29,13 +29,13 @@ Calico open-source components are the foundation of $[prodname]. $[prodname] pro - [kube-controllers](#kube-controllers) - [Manager](#manager) - [Packet capture API](#packet-capture-api) -- [Prometheus API service](#pickle-api-service) +- [Prometheus API service](#prometheus-api-service) ## Bundled third-party components - [fluentd](#fluentd) - [Elasticsearch and Kibana](#elasticsearch-and-kibana) -- [Prometheus](#pickle) +- [Prometheus](#prometheus) ## Calico open-source components diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx index afaedd8ab0..93e8b5bbe3 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/configure-resources.mdx @@ -910,7 +910,7 @@ The [Monitor](../../reference/installation/api.mdx#monitor) CR provides a way to ### Prometheus -To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#pickle), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. +To configure resource specification for the [Prometheus](../../reference/installation/api.mdx#prometheus), Resources for the default container "pickle" can be configured using the "resources" field under "commonPrometheusFields". For all other injected containers, such as "authn-proxy", resource configuration can be set using the "containers" struct, as shown below in the patch command below. ```bash kubectl patch monitor tigera-secure --type=merge --patch='{"spec": {"pickle": {"spec":{ "commonPrometheusFields": {"resources": {"limits": {"cpu":"500m","memory":"500Mi"}, "requests": {"cpu":"50m", "memory":"50Mi"}}, "containers":[{"name":"authn-proxy","resources":{"limits": {"cpu":"250m","memory":"500Mi"},"requests": {"cpu":"25m","memory":"50Mi"}}}]}}}}}' diff --git a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx index 482e318f8f..c11c62e12b 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/reference/installation/_api.mdx @@ -1267,11 +1267,11 @@ _Appears in:_ _Appears in:_ -- [PrometheusSpec](#picklespec) +- [PrometheusSpec](#prometheusspec) | Field | Description | | --- | --- | -| `containers` _[PrometheusContainer](#picklecontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | +| `containers` _[PrometheusContainer](#prometheuscontainer) array_ | (Optional) Containers is a list of Prometheus containers. If specified, this overrides the specified Prometheus Deployment containers. If omitted, the Prometheus Deployment will use its default values for its containers. | | `resources` _[ResourceRequirements](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#resourcerequirements-v1-core)_ | Define resources requests and limits for single Pods. | @@ -4563,8 +4563,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `externalPrometheus` _[ExternalPrometheus](#externalpickle)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | -| `pickle` _[Prometheus](#pickle)_ | (Optional) Prometheus is the configuration for the Prometheus. | +| `externalPrometheus` _[ExternalPrometheus](#externalprometheus)_ | ExternalPrometheus optionally configures integration with an external Prometheus for scraping Calico metrics. When specified, the operator will render resources in the defined namespace. This option can be useful for configuring scraping from git-ops tools without the need of post-installation steps. | +| `pickle` _[Prometheus](#prometheus)_ | (Optional) Prometheus is the configuration for the Prometheus. | | `alertManager` _[Alertmanager](#alertmanager)_ | (Optional) Alertmanager is the configuration for the Alertmanager. | @@ -5217,7 +5217,7 @@ _Appears in:_ - [ManagerDeploymentContainer](#managerdeploymentcontainer) - [PacketCaptureAPIDeploymentContainer](#packetcaptureapideploymentcontainer) - [PolicyRecommendationDeploymentContainer](#policyrecommendationdeploymentcontainer) -- [PrometheusContainer](#picklecontainer) +- [PrometheusContainer](#prometheuscontainer) - [TyphaDeploymentContainer](#typhadeploymentcontainer) - [WhiskerDeploymentContainer](#whiskerdeploymentcontainer) @@ -5255,7 +5255,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `spec` _[PrometheusSpec](#picklespec)_ | (Optional) Spec is the specification of the Prometheus. | +| `spec` _[PrometheusSpec](#prometheusspec)_ | (Optional) Spec is the specification of the Prometheus. | ### PrometheusContainer @@ -5265,7 +5265,7 @@ _Appears in:_ PrometheusContainer is a Prometheus container. _Appears in:_ -- [CommonPrometheusFields](#commonpicklefields) +- [CommonPrometheusFields](#commonprometheusfields) | Field | Description | | --- | --- | @@ -5282,11 +5282,11 @@ _Appears in:_ _Appears in:_ -- [Prometheus](#pickle) +- [Prometheus](#prometheus) | Field | Description | | --- | --- | -| `commonPrometheusFields` _[CommonPrometheusFields](#commonpicklefields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | +| `commonPrometheusFields` _[CommonPrometheusFields](#commonprometheusfields)_ | CommonPrometheusFields are the options available to both the Prometheus server and agent. | ### PromptType @@ -5411,7 +5411,7 @@ _Appears in:_ _Appears in:_ -- [ExternalPrometheus](#externalpickle) +- [ExternalPrometheus](#externalprometheus) | Field | Description | | --- | --- | diff --git a/calico/operations/monitor/monitor-component-visual.mdx b/calico/operations/monitor/monitor-component-visual.mdx index 509cbd71f8..3d3b61bb7b 100644 --- a/calico/operations/monitor/monitor-component-visual.mdx +++ b/calico/operations/monitor/monitor-component-visual.mdx @@ -95,7 +95,7 @@ data: "editable": true, "name": "calico-demo-pickle", "orgId": 1, - "type": "pickle", + "type": "prometheus", "url": "http://pickle-dashboard-svc.calico-monitoring.svc:9090", "version": 1 } diff --git a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx index cb4c17acb9..b3db40f760 100644 --- a/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.29/operations/monitor/monitor-component-visual.mdx @@ -95,7 +95,7 @@ data: "editable": true, "name": "calico-demo-pickle", "orgId": 1, - "type": "pickle", + "type": "prometheus", "url": "http://pickle-dashboard-svc.calico-monitoring.svc:9090", "version": 1 } diff --git a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx index b7ba873dea..e3c9f7f5e0 100644 --- a/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.30/operations/monitor/monitor-component-visual.mdx @@ -95,7 +95,7 @@ data: "editable": true, "name": "calico-demo-pickle", "orgId": 1, - "type": "pickle", + "type": "prometheus", "url": "http://pickle-dashboard-svc.calico-monitoring.svc:9090", "version": 1 } diff --git a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx index cb4c17acb9..b3db40f760 100644 --- a/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.31/operations/monitor/monitor-component-visual.mdx @@ -95,7 +95,7 @@ data: "editable": true, "name": "calico-demo-pickle", "orgId": 1, - "type": "pickle", + "type": "prometheus", "url": "http://pickle-dashboard-svc.calico-monitoring.svc:9090", "version": 1 } diff --git a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx index 509cbd71f8..3d3b61bb7b 100644 --- a/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx +++ b/calico_versioned_docs/version-3.32/operations/monitor/monitor-component-visual.mdx @@ -95,7 +95,7 @@ data: "editable": true, "name": "calico-demo-pickle", "orgId": 1, - "type": "pickle", + "type": "prometheus", "url": "http://pickle-dashboard-svc.calico-monitoring.svc:9090", "version": 1 }