Cc191 rn

calico-cloud_versioned_docs/version-19-1/release-notes/index.mdx

@@ -5,12 +5,9 @@ title: Release notes
 
 # Calico Cloud release notes
 
-## April DD, 2024 (version 19.1.0)
+## April 2, 2024 (version 19.1.0)
 
-### Bug fixes
-
-* Bug 1
-* Bug 2
+This release includes bug fixes and enhancements.
 
 ## February 28, 2024 (version 19.0.0)
 

calico-enterprise/_includes/components/InstallAKS.js

@@ -45,17 +45,6 @@ export default function InstallAKS(props) {
     --type=kubernetes.io/dockerconfigjson -n tigera-operator \\
     --from-file=.dockerconfigjson=<path/to/pull/secret>`}
           </CodeBlock>
-          <p>
-            For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and then
-            patch the deployment.
-          </p>
-          <CodeBlock>
-            {`kubectl create secret generic tigera-pull-secret \\
-    --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-    --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-          </CodeBlock>
         </li>
         <li>
           <p>
@@ -166,17 +155,6 @@ spec:
     --type=kubernetes.io/dockerconfigjson -n tigera-operator \\
     --from-file=.dockerconfigjson=<path/to/pull/secret>`}
           </CodeBlock>
-          <p>
-            For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and then
-            patch the deployment.
-          </p>
-          <CodeBlock>
-            {`kubectl create secret generic tigera-pull-secret \\
-    --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-    --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-          </CodeBlock>
         </li>
         <li>
           <p>

calico-enterprise/_includes/components/InstallEKS.js

@@ -47,17 +47,6 @@ export default function InstallEKS(props) {
     --type=kubernetes.io/dockerconfigjson -n tigera-operator \\
     --from-file=.dockerconfigjson=<path/to/pull/secret>`}
           </CodeBlock>
-          <p>
-            For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and then
-            patch the deployment.
-          </p>
-          <CodeBlock>
-            {`kubectl create secret generic tigera-pull-secret \\
-    --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-    --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-          </CodeBlock>
         </li>
         <li>
           <p>
@@ -217,17 +206,6 @@ spec:
     --type=kubernetes.io/dockerconfigjson -n tigera-operator \\
     --from-file=.dockerconfigjson=<path/to/pull/secret>`}
           </CodeBlock>
-          <p>
-            For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and then
-            patch the deployment.
-          </p>
-          <CodeBlock>
-            {`kubectl create secret generic tigera-pull-secret \\
-    --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-    --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-          </CodeBlock>
         </li>
         <li>
           <p>

calico-enterprise/_includes/components/InstallGKE.js

@@ -46,17 +46,6 @@ export default function InstallGKE(props) {
     --type=kubernetes.io/dockerconfigjson -n tigera-operator \\
     --from-file=.dockerconfigjson=<path/to/pull/secret>`}
           </CodeBlock>
-          <p>
-            For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and then
-            patch the deployment.
-          </p>
-          <CodeBlock>
-            {`kubectl create secret generic tigera-pull-secret \\
-    --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-    --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-          </CodeBlock>
         </li>
         <li>
           <p>

calico-enterprise/_includes/components/InstallGeneric.js

@@ -51,17 +51,6 @@ export default function InstallGeneric(props) {
   --type=kubernetes.io/dockerconfigjson -n tigera-operator \\
   --from-file=.dockerconfigjson=<path/to/pull/secret>`}
           </CodeBlock>
-          <p>
-            For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and then
-            patch the deployment.
-          </p>
-          <CodeBlock>
-            {`kubectl create secret generic tigera-pull-secret \\
-  --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-  --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-  -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-          </CodeBlock>
         </li>
         <li>
           (Optional) If your cluster architecture requires any custom{' '}

calico-enterprise/_includes/components/OpenShiftPrometheusOperator.js

@@ -23,14 +23,6 @@ export default function OpenShiftPrometheusOperator(props) {
         {props.operation === 'install'
             ? <CodeBlock language='bash'>oc create -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml</CodeBlock>
             : <CodeBlock language='bash'>oc apply -f {filesUrl}/manifests/ocp/tigera-prometheus-operator.yaml</CodeBlock>}
-      <p>
-        Create the pull secret in the <code>tigera-prometheus</code> namespace and then patch the Prometheus operator
-        deployment. Use the image pull secret provided to you by Tigera support representative.
-      </p>
-      <CodeBlock language='bash'>
-        {`${notOSCodeBlock}oc patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-      </CodeBlock>
     </>
   );
 }

calico-enterprise/_includes/components/UpgradeOperatorSimple.js

@@ -100,17 +100,6 @@ export default function UpgradeOperatorSimple(props) {
   } \\
   --from-file=.dockerconfigjson=<path/to/pull/secret>`}
             </CodeBlock>
-            <p>
-              For the Prometheus operator, create the pull secret in the <code>tigera-prometheus</code> namespace and
-              then patch the deployment.
-            </p>
-            <CodeBlock>
-              {`kubectl create secret generic tigera-pull-secret \\
-    --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \\
-    --from-file=.dockerconfigjson=<path/to/pull/secret>
-kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \\
-    -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'`}
-            </CodeBlock>
           </li>
         </When>
 

calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx

@@ -84,16 +84,6 @@ The geeky details of what you get:
        --from-file=.dockerconfigjson=<path/to/pull/secret>
    ```
 
-   For the Prometheus operator, create the pull secret in the `tigera-prometheus` namespace and then patch the deployment.
-
-   ```bash
-   kubectl create secret generic tigera-pull-secret \
-       --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \
-       --from-file=.dockerconfigjson=<path/to/pull/secret>
-   kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \
-       -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'
-   ```
-
 1. Install any extra [{{prodname}} resources](../../reference/resources/index.mdx) needed at cluster start using [calicoctl](../../reference/clis/calicoctl/overview.mdx).
 
 1. Install the Tigera custom resources. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx).

calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx

@@ -115,16 +115,6 @@ A Linux host that meets the following requirements.
        --from-file=.dockerconfigjson=<path/to/pull/secret>
    ```
 
-   For the Prometheus operator, create the pull secret in the `tigera-prometheus` namespace and then patch the deployment.
-
-   ```bash
-   kubectl create secret generic tigera-pull-secret \
-       --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \
-       --from-file=.dockerconfigjson=<path/to/pull/secret>
-   kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \
-       -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'
-   ```
-
 1. Install the Tigera custom resources. For more information on configuration options available in this manifest, see [the installation reference](../../../reference/installation/api.mdx).
 
    ```bash

calico-enterprise/getting-started/install-on-clusters/rancher.mdx

@@ -83,16 +83,6 @@ The geeky details of what you get:
        --from-file=.dockerconfigjson=<path/to/pull/secret>
    ```
 
-   For the Prometheus operator, create the pull secret in the `tigera-prometheus` namespace and then patch the deployment.
-
-   ```bash
-   kubectl create secret generic tigera-pull-secret \
-       --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \
-       --from-file=.dockerconfigjson=<path/to/pull/secret>
-   kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \
-       -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'
-   ```
-
 1. Install any extra [{{prodname}} resources](../../reference/resources/index.mdx) needed at cluster start using [calicoctl](../../reference/clis/calicoctl/overview.mdx).
 
 1. Install the Tigera custom resources. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx).

calico-enterprise/getting-started/install-on-clusters/rke2.mdx

@@ -80,16 +80,6 @@ The geeky details of what you get:
        --from-file=.dockerconfigjson=<path/to/pull/secret>
    ```
 
-   For the Prometheus operator, create the pull secret in the `tigera-prometheus` namespace and then patch the deployment.
-
-   ```bash
-   kubectl create secret generic tigera-pull-secret \
-       --type=kubernetes.io/dockerconfigjson -n tigera-prometheus \
-       --from-file=.dockerconfigjson=<path/to/pull/secret>
-   kubectl patch deployment -n tigera-prometheus calico-prometheus-operator \
-       -p '{"spec":{"template":{"spec":{"imagePullSecrets":[{"name": "tigera-pull-secret"}]}}}}'
-   ```
-
 1. Install any extra [Calico resources](../../reference/resources/index.mdx) needed at cluster start using [calicoctl](../../reference/clis/calicoctl/overview.mdx).
 
 1. Install the Tigera custom resources. For more information on configuration options available, see [the installation reference](../../reference/installation/api.mdx).