Skip to main content

 Permanently disable warning banner - " Kubernetes integration capabilities including TKG integration and TMC integration will be deprecated and removed from the product in a future release."


Products

VMware Aria Suite

Issue/Introduction

How to permanently disable warning banner - " Kubernetes integration capabilities including TKG integration and TMC integration will be deprecated and removed from the product in a future release.Customers should make plans to stop using this functionality and start leveraging Cloud Consumption Interface"  

When a user clicks the  X  icon on the banner, the banner is dismissed for the browser session. A new session for example is created when the address of the app is put in a different browser tab/ browser.

When a new session starts the banner is displayed again.

Environment

Aria Automation 8.18

Cause

A medium to communicate with the customer " Announcing intent to deprecate specific Kubernetes automation capabilities " . Also mentioned in the release notes for Aria Automation 8.18 under section.

VMware by Broadcom is announcing the planned deprecation of Kubernetes integration capabilities, including the TKG integration and TMC integration documented under How do I work with Kubernetes in Automation Assembler. The actual deprecation and removal of these capabilities from the product will happen in a future release. Customers are encouraged to adopt the Cloud Consumption interface (CCI) and vSphere TKG IaaS service. 

Resolution

Option 1: Using Curl Command

The banner itself could be disabled permanently using this http request

curl -k 'https://{fqdn}/provisioning/config/toggles'  -H 'Accept: application/json, text/plain, '  -H 'Authorization: Bearer {bearer_token}'  -H 'Content-Type: application/json' -H 'pragma: xn-force-index-update' --data-raw '{"key":"ui.disable.deprecation.alerts","value":"true"}'

** Where {fqdn} and {bearer_token} need to be replaced accordingly.

Option 2: Using API Call

  1. Follow this KB to get the bearer token.
  2. Open Postman and connect to https://{fqdn}/provisioning/config/toggles
  3. Use the bearer token from step 1 and put it in the Autorization tab 
  4. In the header tab make sure the key: value pair is Content-Type and application/jason
  5. In the body set as {"key":"ui.disable.deprecation.alerts","value":"false"} and click send. Make sure that we get response 200.
  6. Logout of Aria Automation and log back in, you should not see the banner anymore.

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...
Post a Comment
Read more