docs: update Getting Started AWS and GCP screenshots DOC-1394

_partials/getting-started/_cluster_profile_import_aws.mdx

@@ -37,9 +37,9 @@ partial_name: import-hello-uni-aws
           "name": "kubernetes",
           "type": "spectro",
           "layer": "k8s",
-          "version": "1.27.15",
-          "tag": "1.27.x",
-          "values": "# spectrocloud.com/enabled-presets: Kube Controller Manager:loopback-ctrlmgr,Kube Scheduler:loopback-scheduler\npack:\n  content:\n    images:\n      - image: registry.k8s.io/coredns/coredns:v1.10.1\n      - image: registry.k8s.io/etcd:3.5.12-0\n      - image: registry.k8s.io/kube-apiserver:v1.27.15\n      - image: registry.k8s.io/kube-controller-manager:v1.27.15\n      - image: registry.k8s.io/kube-proxy:v1.27.15\n      - image: registry.k8s.io/kube-scheduler:v1.27.15\n      - image: registry.k8s.io/pause:3.9\n      - image: registry.k8s.io/pause:3.8\n  #CIDR Range for Pods in cluster\n  # Note : This must not overlap with any of the host or service network\n  podCIDR: \"192.168.0.0/16\"\n  #CIDR notation IP range from which to assign service cluster IPs\n  # Note : This must not overlap with any IP ranges assigned to nodes for pods.\n  serviceClusterIpRange: \"10.96.0.0/12\"\n  # serviceDomain: \"cluster.local\"\n\nkubeadmconfig:\n  apiServer:\n    extraArgs:\n      # Note : secure-port flag is used during kubeadm init. Do not change this flag on a running cluster\n      secure-port: \"6443\"\n      anonymous-auth: \"true\"\n      profiling: \"false\"\n      disable-admission-plugins: \"AlwaysAdmit\"\n      default-not-ready-toleration-seconds: \"60\"\n      default-unreachable-toleration-seconds: \"60\"\n      enable-admission-plugins: \"AlwaysPullImages,NamespaceLifecycle,ServiceAccount,NodeRestriction,PodSecurity\"\n      admission-control-config-file: \"/etc/kubernetes/pod-security-standard.yaml\"\n      audit-log-path: /var/log/apiserver/audit.log\n      audit-policy-file: /etc/kubernetes/audit-policy.yaml\n      audit-log-maxage: \"30\"\n      audit-log-maxbackup: \"10\"\n      audit-log-maxsize: \"100\"\n      authorization-mode: RBAC,Node\n      tls-cipher-suites: \"TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256\"\n    extraVolumes:\n      - name: audit-log\n        hostPath: /var/log/apiserver\n        mountPath: /var/log/apiserver\n        pathType: DirectoryOrCreate\n      - name: audit-policy\n        hostPath: /etc/kubernetes/audit-policy.yaml\n        mountPath: /etc/kubernetes/audit-policy.yaml\n        readOnly: true\n        pathType: File\n      - name: pod-security-standard\n        hostPath: /etc/kubernetes/pod-security-standard.yaml\n        mountPath: /etc/kubernetes/pod-security-standard.yaml\n        readOnly: true\n        pathType: File\n  controllerManager:\n    extraArgs:\n      profiling: \"false\"\n      terminated-pod-gc-threshold: \"25\"\n      use-service-account-credentials: \"true\"\n      feature-gates: \"RotateKubeletServerCertificate=true\"\n  scheduler:\n    extraArgs:\n      profiling: \"false\"\n  kubeletExtraArgs:\n    read-only-port : \"0\"\n    event-qps: \"0\"\n    feature-gates: \"RotateKubeletServerCertificate=true\"\n    protect-kernel-defaults: \"true\"\n    rotate-server-certificates: \"true\"\n    tls-cipher-suites: \"TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256\"\n  files:\n    - path: hardening/audit-policy.yaml\n      targetPath: /etc/kubernetes/audit-policy.yaml\n      targetOwner: \"root:root\"\n      targetPermissions: \"0600\"\n    - path: hardening/90-kubelet.conf\n      targetPath: /etc/sysctl.d/90-kubelet.conf\n      targetOwner: \"root:root\"\n      targetPermissions: \"0600\"\n    - targetPath: /etc/kubernetes/pod-security-standard.yaml\n      targetOwner: \"root:root\"\n      targetPermissions: \"0600\"\n      content: |\n        apiVersion: apiserver.config.k8s.io/v1\n        kind: AdmissionConfiguration\n        plugins:\n        - name: PodSecurity\n          configuration:\n            apiVersion: pod-security.admission.config.k8s.io/v1\n            kind: PodSecurityConfiguration\n            defaults:\n              enforce: \"baseline\"\n              enforce-version: \"v1.27\"\n              audit: \"baseline\"\n              audit-version: \"v1.27\"\n              warn: \"restricted\"\n              warn-version: \"v1.27\"\n              audit: \"restricted\"\n              audit-version: \"v1.27\"\n            exemptions:\n              # Array of authenticated usernames to exempt.\n              usernames: []\n              # Array of runtime class names to exempt.\n              runtimeClasses: []\n              # Array of namespaces to exempt.\n              namespaces: [kube-system]\n\n  preKubeadmCommands:\n    # For enabling 'protect-kernel-defaults' flag to kubelet, kernel parameters changes are required\n    - 'echo \"====> Applying kernel parameters for Kubelet\"'\n    - 'sysctl -p /etc/sysctl.d/90-kubelet.conf'\n  postKubeadmCommands:\n    - 'chmod 600 /var/lib/kubelet/config.yaml'\n    #- 'echo \"List of post kubeadm commands to be executed\"'\n\n# Client configuration to add OIDC based authentication flags in kubeconfig\n#clientConfig:\n  #oidc-issuer-url: \"{{ .spectro.pack.kubernetes.kubeadmconfig.apiServer.extraArgs.oidc-issuer-url }}\"\n  #oidc-client-id: \"{{ .spectro.pack.kubernetes.kubeadmconfig.apiServer.extraArgs.oidc-client-id }}\"\n  #oidc-client-secret: 1gsranjjmdgahm10j8r6m47ejokm9kafvcbhi3d48jlc3rfpprhv\n  #oidc-extra-scope: profile,email",
+          "version": "1.29.8",
+          "tag": "1.29.x",
+          "values": "# spectrocloud.com/enabled-presets: Kube Controller Manager:loopback-ctrlmgr,Kube Scheduler:loopback-scheduler\npack:\n  content:\n    images:\n      - image: registry.k8s.io/coredns/coredns:v1.11.1\n      - image: registry.k8s.io/etcd:3.5.12-0\n      - image: registry.k8s.io/kube-apiserver:v1.29.8\n      - image: registry.k8s.io/kube-controller-manager:v1.29.8\n      - image: registry.k8s.io/kube-proxy:v1.29.8\n      - image: registry.k8s.io/kube-scheduler:v1.29.8\n      - image: registry.k8s.io/pause:3.9\n      - image: registry.k8s.io/pause:3.8\n  #CIDR Range for Pods in cluster\n  # Note : This must not overlap with any of the host or service network\n  podCIDR: \"192.168.0.0/16\"\n  #CIDR notation IP range from which to assign service cluster IPs\n  # Note : This must not overlap with any IP ranges assigned to nodes for pods.\n  serviceClusterIpRange: \"10.96.0.0/12\"\n  # serviceDomain: \"cluster.local\"\n\nkubeadmconfig:\n  apiServer:\n    extraArgs:\n      # Note : secure-port flag is used during kubeadm init. Do not change this flag on a running cluster\n      secure-port: \"6443\"\n      anonymous-auth: \"true\"\n      profiling: \"false\"\n      disable-admission-plugins: \"AlwaysAdmit\"\n      default-not-ready-toleration-seconds: \"60\"\n      default-unreachable-toleration-seconds: \"60\"\n      enable-admission-plugins: \"AlwaysPullImages,NamespaceLifecycle,ServiceAccount,NodeRestriction,PodSecurity\"\n      admission-control-config-file: \"/etc/kubernetes/pod-security-standard.yaml\"\n      audit-log-path: /var/log/apiserver/audit.log\n      audit-policy-file: /etc/kubernetes/audit-policy.yaml\n      audit-log-maxage: \"30\"\n      audit-log-maxbackup: \"10\"\n      audit-log-maxsize: \"100\"\n      authorization-mode: RBAC,Node\n      tls-cipher-suites: \"TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256\"\n    extraVolumes:\n      - name: audit-log\n        hostPath: /var/log/apiserver\n        mountPath: /var/log/apiserver\n        pathType: DirectoryOrCreate\n      - name: audit-policy\n        hostPath: /etc/kubernetes/audit-policy.yaml\n        mountPath: /etc/kubernetes/audit-policy.yaml\n        readOnly: true\n        pathType: File\n      - name: pod-security-standard\n        hostPath: /etc/kubernetes/pod-security-standard.yaml\n        mountPath: /etc/kubernetes/pod-security-standard.yaml\n        readOnly: true\n        pathType: File\n  controllerManager:\n    extraArgs:\n      profiling: \"false\"\n      terminated-pod-gc-threshold: \"25\"\n      use-service-account-credentials: \"true\"\n      feature-gates: \"RotateKubeletServerCertificate=true\"\n  scheduler:\n    extraArgs:\n      profiling: \"false\"\n  kubeletExtraArgs:\n    read-only-port: \"0\"\n    event-qps: \"0\"\n    feature-gates: \"RotateKubeletServerCertificate=true\"\n    protect-kernel-defaults: \"true\"\n    rotate-server-certificates: \"true\"\n    tls-cipher-suites: \"TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256\"\n  files:\n    - path: hardening/audit-policy.yaml\n      targetPath: /etc/kubernetes/audit-policy.yaml\n      targetOwner: \"root:root\"\n      targetPermissions: \"0600\"\n    - path: hardening/90-kubelet.conf\n      targetPath: /etc/sysctl.d/90-kubelet.conf\n      targetOwner: \"root:root\"\n      targetPermissions: \"0600\"\n    - targetPath: /etc/kubernetes/pod-security-standard.yaml\n      targetOwner: \"root:root\"\n      targetPermissions: \"0600\"\n      content: |\n        apiVersion: apiserver.config.k8s.io/v1\n        kind: AdmissionConfiguration\n        plugins:\n        - name: PodSecurity\n          configuration:\n            apiVersion: pod-security.admission.config.k8s.io/v1\n            kind: PodSecurityConfiguration\n            defaults:\n              enforce: \"baseline\"\n              enforce-version: \"v1.29\"\n              audit: \"baseline\"\n              audit-version: \"v1.29\"\n              warn: \"restricted\"\n              warn-version: \"v1.29\"\n              audit: \"restricted\"\n              audit-version: \"v1.29\"\n            exemptions:\n              # Array of authenticated usernames to exempt.\n              usernames: []\n              # Array of runtime class names to exempt.\n              runtimeClasses: []\n              # Array of namespaces to exempt.\n              namespaces: [kube-system]\n\n  preKubeadmCommands:\n    # For enabling 'protect-kernel-defaults' flag to kubelet, kernel parameters changes are required\n    - 'echo \"====> Applying kernel parameters for Kubelet\"'\n    - 'sysctl -p /etc/sysctl.d/90-kubelet.conf'\n  \n  postKubeadmCommands:\n    - 'chmod 600 /var/lib/kubelet/config.yaml'\n    # - 'echo \"List of post kubeadm commands to be executed\"'\n\n# Client configuration to add OIDC based authentication flags in kubeconfig\n#clientConfig:\n  #oidc-issuer-url: \"{{ .spectro.pack.kubernetes.kubeadmconfig.apiServer.extraArgs.oidc-issuer-url }}\"\n  #oidc-client-id: \"{{ .spectro.pack.kubernetes.kubeadmconfig.apiServer.extraArgs.oidc-client-id }}\"\n  #oidc-client-secret: 1gsranjjmdgahm10j8r6m47ejokm9kafvcbhi3d48jlc3rfpprhv\n  #oidc-extra-scope: profile,email",
           "registry": {
             "metadata": {
               "uid": "5eecc89d0b150045ae661cef",
@@ -88,9 +88,9 @@ partial_name: import-hello-uni-aws
           "name": "hello-universe",
           "type": "oci",
           "layer": "addon",
-          "version": "1.1.3",
-          "tag": "1.1.3",
-          "values": "# spectrocloud.com/enabled-presets: Backend:disable-api\npack:\n  content:\n    images:\n      - image: ghcr.io/spectrocloud/hello-universe:1.1.3\n  spectrocloud.com/install-priority: 0\n\nmanifests:\n  hello-universe:\n    images:\n      hellouniverse: ghcr.io/spectrocloud/hello-universe:1.1.3\n    apiEnabled: false\n    namespace: hello-universe\n    port: 8080\n    replicas: 1",
+          "version": "1.2.0",
+          "tag": "1.2.0",
+          "values": "# spectrocloud.com/enabled-presets: Backend:disable-api\npack:\n  content:\n    images:\n      - image: ghcr.io/spectrocloud/hello-universe:1.2.0\n  spectrocloud.com/install-priority: 0\n\nmanifests:\n  hello-universe:\n    images:\n      hellouniverse: ghcr.io/spectrocloud/hello-universe:1.2.0\n    apiEnabled: false\n    namespace: hello-universe\n    port: 8080\n    replicas: 1",
           "registry": {
             "metadata": {
               "uid": "64eaff5630402973c4e1856a",

docs/docs-content/getting-started/aws/create-cluster-profile.md

@@ -37,8 +37,6 @@ Log in to [Palette](https://console.spectrocloud.com) and navigate to the left *
 view the cluster profile page. You can view the list of available cluster profiles. To create a cluster profile, click
 on **Add Cluster Profile**.
 
-![View of the cluster Profiles page](/getting-started/getting-started_create-cluster-profile_profile_list_view.webp)
-
 Follow the wizard to create a new profile.
 
 In the **Basic Information** section, assign the name **aws-profile**, a brief profile description, select the type as
@@ -57,9 +55,9 @@ For this tutorial, use the following packs:
 | Pack Name      | Version | Layer            |
 | -------------- | ------- | ---------------- |
 | ubuntu-aws LTS | 22.4.x  | Operating System |
-| Kubernetes     | 1.27.x  | Kubernetes       |
-| cni-calico     | 3.26.x  | Network          |
-| csi-aws-ebs    | 1.22.x  | Storage          |
+| Kubernetes     | 1.29.x  | Kubernetes       |
+| cni-calico     | 3.27.x  | Network          |
+| csi-aws-ebs    | 1.26.x  | Storage          |
 
 As you fill out the information for each layer, click on **Next** to proceed to the next layer.
 
@@ -77,7 +75,7 @@ Navigate to the left **Main Menu** and select **Profiles**. Select the cluster p
 Click on **Add New Pack** at the top of the page.
 
 Select the **Palette Community Registry** from the **Registry** dropdown. Then, click on the latest **Hello Universe**
-pack with version **v1.1.2**.
+pack with version **v1.2.0**.
 
 ![Screenshot of hello universe pack](/getting-started/aws/getting-started_create-cluster-profile_add-pack.webp)
 

docs/docs-content/getting-started/aws/deploy-k8s-cluster.md

@@ -135,8 +135,7 @@ moments before clicking on the service URL to prevent the browser from caching a
 
 ![Image that shows the cluster overview of the Hello Universe Frontend Cluster](/getting-started/getting-started_deploy-k8s-cluster_hello-universe-with-api.webp)
 
-Welcome to Hello Universe, a demo application to help you learn more about Palette and its features. Feel free to click
-on the logo to increase the counter and for a fun image change.
+Welcome to Spacetastic's astronomy education platform. Feel free to explore the pages and learn more about space. The statistics page offers information on visitor counts on your deployed cluster. 
 
 You have deployed your first application to a cluster managed by Palette. Your first application is a three-tier
 application with a frontend, API server, and Postgres database.

docs/docs-content/getting-started/aws/deploy-manage-k8s-cluster-tf.md

@@ -226,7 +226,7 @@ The table below displays the packs deployed in each version of the cluster profi
 | Kubernetes    | `kubernetes`    | `1.29.0`    | :white_check_mark:         | :white_check_mark:         |
 | Network       | `cni-calico`    | `3.27.0`    | :white_check_mark:         | :white_check_mark:         |
 | Storage       | `csi-aws-ebs`   | `1.26.1`    | :white_check_mark:         | :white_check_mark:         |
-| App Services  | `hellouniverse` | `1.1.2`     | :white_check_mark:         | :white_check_mark:         |
+| App Services  | `hellouniverse` | `1.2.0`     | :white_check_mark:         | :white_check_mark:         |
 | App Services  | `cost-analyzer` | `1.103.3`   | :x:                        | :white_check_mark:         |
 
 The Hello Universe pack has two configured [presets](../../glossary-all.md#presets). The first preset deploys a
@@ -544,8 +544,7 @@ moments before clicking on the service URL to prevent the browser from caching a
 
 ![Deployed application](/getting-started/aws/getting-started_deploy-manage-k8s-cluster_hello-universe-w-api.webp)
 
-Welcome to Hello Universe, a demo application developed to help you learn more about Palette and its features. Feel free
-to click on the logo to increase the counter and for a fun image change.
+Welcome to Spacetastic's astronomy education platform. Feel free to explore the pages and learn more about space. The statistics page offers information on visitor counts on your deployed cluster.
 
 ## Version Cluster Profiles
 

docs/docs-content/getting-started/aws/scale-secure-cluster.md

@@ -191,10 +191,10 @@ Click on the version drop-down and select **Create new version**. The version cr
 Fill in **1.1.0** in the **Version** input field. Then, click on **Confirm**. The new cluster profile version is created
 with the same layers as version **1.0.0**.
 
-Select the **kubernetes 1.27.x** layer of the profile. The pack manifest editor appears.
+Select the **kubernetes 1.29.x** layer of the profile. The pack manifest editor appears.
 
 Click on the **Pack Version** dropdown. All of the available versions of the **Palette eXtended Kubernetes** pack
-appear. The cluster profile is configured to use the latest patch version of **Kubernetes 1.27**.
+appear. The cluster profile is configured to use the latest patch version of **Kubernetes 1.29**.
 
 ![Cluster profile with all Kubernetes versions](/getting-started/aws/getting-started_scale-secure-cluster_kubernetes-versions.webp)
 
@@ -203,8 +203,8 @@ using Kubernetes version 1.26, you should upgrade to 1.27, before upgrading to v
 the official Kubernetes upgrade guidelines in the
 [Version Skew Policy](https://kubernetes.io/releases/version-skew-policy/) page.
 
-Select **1.28.x** from the version dropdown. This selection follows the Kubernetes upgrade guidelines as the cluster
-profile is using **1.27.x**.
+Select **1.30.x** from the version dropdown. This selection follows the Kubernetes upgrade guidelines as the cluster
+profile is using **1.29.x**.
 
 The manifest editor highlights the changes made by this upgrade. Once you have verified that the upgrade changes
 versions as expected, click on **Confirm changes**.
@@ -237,7 +237,7 @@ application, as Kubernetes swaps the workloads to the upgraded nodes.
 ### Verify the Application
 
 The cluster update completes when the Palette UI marks the cluster profile layers as green and the cluster is in a
-**Healthy** state. The cluster **Overview** page also displays the Kubernetes version as **1.28**. Click on the URL for
+**Healthy** state. The cluster **Overview** page also displays the Kubernetes version as **1.30**. Click on the URL for
 port **:8080** to access the application and verify that your upgraded cluster is functional.
 
 ![Kubernetes upgrade applied](/getting-started/aws/getting-started_scale-secure-cluster_kubernetes-upgrade-applied.webp)