Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion test/integration/manifests/cns/configmap.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -21,5 +21,6 @@ data:
"NodeID": "",
"NodeSyncIntervalInSeconds": 30
},
"ChannelMode": "CRD"
"ChannelMode": "CRD",
"InitializeFromCNI": true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed offline, lets understand how CNS/CNI gets updated on existing E2E clusters, and add a test for scaling new nodes too

}
27 changes: 0 additions & 27 deletions test/integration/manifests/cns/daemonset.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -99,30 +99,3 @@ spec:
configMap:
name: cns-config
serviceAccountName: azure-cns
---
apiVersion: v1
kind: ConfigMap
metadata:
name: cns-config
namespace: kube-system
data:
cns_config.json: |
{
"TelemetrySettings": {
"TelemetryBatchSizeBytes": 16384,
"TelemetryBatchIntervalInSecs": 15,
"RefreshIntervalInSecs": 15,
"DisableAll": false,
"HeartBeatIntervalInMins": 30,
"DebugMode": false,
"SnapshotIntervalInMins": 60
},
"ManagedSettings": {
"PrivateEndpoint": "",
"InfrastructureNetworkID": "",
"NodeID": "",
"NodeSyncIntervalInSeconds": 30
},
"ChannelMode": "CRD",
"InitializeFromCNI": true
}