* The value of minor was incorrectly assumed to be e.g. 14.8-hotfix.20191113 instead of 14+
* adding Jonathan Chauncey's test
* addressing Robbie's comments
log.SetTarget creates the log file under log directory using golang os package. Whenever code sets the log directory, it needed to call SetTarget to create the actual log file under that directory. In the recent logger changes, InitLogger by default set the log directory to the current folder. This created the log file in the current folder. The code then set the log directory to a different location without a subsequent call to log.SetTarget. This resulted into the logger to not find the actual log file in the set log directory.
This fix updates the logger InitLogger function to accept the log directory to create the file in correct log directory. To avoid having such issue, this fix also combines the function calls to set log directory and set target into a single function. This prevents any out of order calls resulting into such issue.
* Added AITelemetry support for CNI
* added new files
* added other configs in config file
* fixed ut
* updated disableall similar to cns
* added container name to report
* addressed review comments
* addressed review comments
* added check for azure environment
* added log
* close log handle in unit test
* addressed review comments
* addressed review comments
* fixed a condition
* keep the netagent channel for logs
* fixed error
* addressed review comments
* update e2e to reuse pipeline artifacts
* install ginkgo
* update e2e config for apiserver
* add clean up step
* aks-engine version
* aks-engine version
* aks-engine version
* aks-engine version
* aks-engine version
* aks-engine version
* aks-engine version
* aks-engine version
* added config option for disabling iptable lock
* added log for iptable and ebtable version
* moved logging dependency package details to platform specific file
* poll api-server version for a minute before panicking
* always add namespace set, when adding nw policy
* create the ns set in add pod, if add namespace has not been called yet
enableExactMatchForPodName flag is missing in the multitenancy config
for windows. This changes adds this missing flag in the config.
Default set to true
* give precedence to drop rules (over allow)
* - Moving kube-system-chain above target-sets-chain
- Add drop entry at the end of Ingress-From and Egress-To chains when there are non Allow-All* entries
* write logs to stdout (and log file) so that we can see logs via kubectl
* removing kube-system chain and fixing tests
* removing telemetry buffer
* added removeorphanlockfile function
* remove lock file if process holding that exited
* addressed comments
* addressed comments and added a condition to check get process cmd is supported
* Addressed comments
fixed trim line ending
* updated log
* added script to invoke cni with dns as runtime config
* renamed file
* added usage example
* update script to take dns suffix
* addressed comments
* added comments
* parameterized few variables to make it work for containerd runtime
* updated desc
AzureNetworkContainer.exe is in the same location as azure-cns.exe but
if CNS is invoked from a process which is in a different working directory,
os.stat called in CNS points to the directory of parent process. This change
fixes the logic to point to the correct working directory.
* Save enable snat on host settings after querying NMagent version
* Adding changes to exclude outbound snat for win cni if new NMAgent is running
* try to acquire lock file when writing to disableSnatOnHost.json
* addressed some of Tamilmani's comments
* Adding snat for DNS if current NMAgent does not support it yet
* Adding DNS NAT changes for Windows CNI
* vendoring HCSShim changes that support destination based SNATing
* Reverting k8s.io/api dependencies from master branch to last working version
* Addressing Tamilmani's comments
* syncing with an older version of k8s.io dependencies
* verify valid windows version before Dns NAT.
* only remove snat on windows when host has full support
* addressing Tamilmani's comments
* addressing Tamilmani's comments
* rebased and re-depped
Expose 2 APIs to publish and unpublish network containers from CNS.
a. PublishNetworkContainer
b. UnpublishNetworkContainer
DNC calls CNS to publish and unpublish the network containers.
* addressed concerns discussed during brownbag session
* updated fields in aitelemetry
* addressed review comments
* flipped the metadata thread field
* fixed compilation errors
* added default refresh timeout
* moved out of for loop
* added unittest
* added disableall field which disables everything(trace,metric)
* removed disable logic from ai package
* added an error check for getting metadata
This PR adds support for host NC bidirectional communication with windows HnsV2. This is supported in multitenant scenario only. AllowHostToNCCommunication and AllowNCToHostCommunication flags are used to enable Host to NC and NC to host communication respectively.
* added application insights telemetry package to send metrics and logs to appinsights
* moved a function common to both packages
acquired a lock before writing to file
* added read write lock as per chandan comment. Addressed jaeryn comments
* fixed telemetry unit test
* defined interface and added appinsights package as vendor to acn
* added vendor package.go(appinsights)
* dependencies of appinsights
* added AI dependencies
* updated unit tests
* addressed review comments
In case of WebApps the NC goal state gets saved with CNS if the loopback adapter creation is successful. This change fixes the bug where the goal state wasn't getting saved because the condition for WebApps containerType would run into default case and error out.
Jaeryn
Mathew Merrick
tamilmani1989
Ashutosh Dubey
Ashvin Deodhar
Vipul Hattiwale
vivekagg-MSFT