You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Append a new matchLabels "clusters.clusternet.io/cluster-id": "c817745f-f46b-4a2b-95fd-86521c81cc79" in the subscription, the original matchLabels "clusters.clusternet.io/cluster-id": "46919132-9639-4c72-a187-975d8cfe0f6c" will lost
☁ ~ k get sub helm-demo -ojson | jq '.spec.subscribers'
[
{
"clusterAffinity": {
"matchLabels": {
"clusters.clusternet.io/cluster-id": "c817745f-f46b-4a2b-95fd-86521c81cc79"
}
}
}
]
What you expected to happen:
☁ ~ k get sub helm-demo -ojson | jq '.spec.subscribers'
[
{
"clusterAffinity": {
"matchLabels": {
"clusters.clusternet.io/cluster-id": "46919132-9639-4c72-a187-975d8cfe0f6c""clusters.clusternet.io/cluster-id": "c817745f-f46b-4a2b-95fd-86521c81cc79"
}
}
}
]
How to reproduce it (as minimally and precisely as possible):
There are 2 managed cluster, and a subscription in my test env.
☁ ~ k get mcls -A
NAMESPACE NAME CLUSTER ID SYNC MODE KUBERNETES READYZ AGE
clusternet-4jxfq clusternet-cluster-l2bmc 46919132-9639-4c72-a187-975d8cfe0f6c Dual v1.21.1 true 23h
clusternet-dwgrd clusternet-cluster-kx2b2 c817745f-f46b-4a2b-95fd-86521c81cc79 Dual v1.21.1 true 23h
☁ ~ cat sub.yaml
apiVersion: apps.clusternet.io/v1alpha1
kind: Subscription
metadata:
name: helm-demo
namespace: default
spec:
subscribers:
- clusterAffinity:
matchLabels:
clusters.clusternet.io/cluster-id: 46919132-9639-4c72-a187-975d8cfe0f6c
feeds:
- apiVersion: apps.clusternet.io/v1alpha1
kind: HelmChart
name: mysql
namespace: default
- apiVersion: apps.clusternet.io/v1alpha1
kind: HelmChart
namespace: default
feedSelector:
matchLabels:
app: wordpress
Apply this subscription, and check hr, looks good so far.
☁ ~ k apply -f sub.yaml
subscription.apps.clusternet.io/helm-demo created
☁ ~ k get hr -A
NAMESPACE NAME CHART VERSION REPO STATUS AGE
clusternet-4jxfq helm-demo-mysql mysql 8.6.2 https://charts.bitnami.com/bitnami deployed 20s
clusternet-4jxfq helm-demo-wordpress wordpress 11.0.17 https://charts.bitnami.com/bitnami deployed 20s
Edit the subscription, and append a new matchLabels clusters.clusternet.io/cluster-id: c817745f-f46b-4a2b-95fd-86521c81cc79 in this sub.
Expect result:,
☁ ~ k get sub helm-demo -ojson | jq '.spec.subscribers'
[
{
"clusterAffinity": {
"matchLabels": {
"clusters.clusternet.io/cluster-id": "46919132-9639-4c72-a187-975d8cfe0f6c""clusters.clusternet.io/cluster-id": "c817745f-f46b-4a2b-95fd-86521c81cc79"
}
}
}
]
After edit subscription,
☁ ~ k get sub helm-demo -ojson | jq '.spec.subscribers'
[
{
"clusterAffinity": {
"matchLabels": {
"clusters.clusternet.io/cluster-id": "c817745f-f46b-4a2b-95fd-86521c81cc79"
}
}
}
]
Anything else we need to know?:
Environment:
Clusternet version:
Clusternet-agent version (user clusternet-agent --version=json):
Clusternet-hub version (user clusternet-hub --version=json): "ghcr.io/clusternet/clusternet-hub:v0.2.0"
What happened:
Append a new matchLabels
"clusters.clusternet.io/cluster-id": "c817745f-f46b-4a2b-95fd-86521c81cc79"
in the subscription, the original matchLabels"clusters.clusternet.io/cluster-id": "46919132-9639-4c72-a187-975d8cfe0f6c"
will lostWhat you expected to happen:
How to reproduce it (as minimally and precisely as possible):
There are 2 managed cluster, and a subscription in my test env.
Apply this subscription, and check hr, looks good so far.
Edit the subscription, and append a new matchLabels
clusters.clusternet.io/cluster-id: c817745f-f46b-4a2b-95fd-86521c81cc79
in this sub.Expect result:,
After edit subscription,
Anything else we need to know?:
Environment:
Clusternet version:
clusternet-agent --version=json
):clusternet-hub --version=json
): "ghcr.io/clusternet/clusternet-hub:v0.2.0"Kubernetes version (use
kubectl version
):This is kind cluster
☁ ~ kind get clusters cluster1 cluster2 hub
cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: