All,
Referencing
https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/compat.html, some
of the distros and hypervisors we support have reached or reaching EOL by end
of this month.
Please review and advise how we should deprecating/remove the following for the
next 4.20 release (i.e. c
I'd like if we keep EL7 for at least one more version, the transition path out
of that is clear now but many cloud operators haven't replaced it yet.
On the rest +1
-Original Message-
From: Rohit Yadav
Sent: Thursday, June 20, 2024 11:43 AM
To: dev@cloudstack.apache.org
Subject: [
+1 what Alex said.
It's kind of wrong, but CentOS7 has such a large install base (generally
and for Cloudstack, too) that I feel deprecating it right away would be
a mistake.
On 2024-06-20 10:45, Alex Mattioli wrote:
I'd like if we keep EL7 for at least one more version, the transition
path
+ Users
Just to be clear, what this thread is about - Deprecating/removing
documentation via the compatibility matrix for a component does not necessarily
mean CloudStack will not work on it, in fact it might (with some additional pkg
installation if required if we decide to transition to JRE17
Hi Vishesh
+1
I tried the same steps as Wei did, but deployed a cks cluster in a vpc network
tier with acl rule of default_allow
1. Create a CKS cluster with k8s 1.28.4 and Select a vpc network
2. Delete cloudstack-kubernetes-provider 1.0.0
kubectl delete -f
https://raw.githubusercontent.com
+1 as well, based on similar test to Wei's.
Good job, Vishesh.
On 2024-06-20 12:34, Kiran Chavala wrote:
Hi Vishesh
+1
I tried the same steps as Wei did, but deployed a cks cluster in a vpc
network tier with acl rule of default_allow
1. Create a CKS cluster with k8s 1.28.4 and Select a vp
By all means, remove CentOS7 and any EOL OS or component from the matrix
and recommendations!
Regards
On 2024-06-20 11:45, Rohit Yadav wrote:
+ Users
Just to be clear, what this thread is about - Deprecating/removing
documentation via the compatibility matrix for a component does not
necess
