-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Health private preview agent #253
base: ci_feature
Are you sure you want to change the base?
Conversation
ci_feature/setup.sh
Outdated
#wget https://github.com/Microsoft/Docker-Provider/releases/download/hotfix-01292019/docker-cimprov-3.0.0-8.universal.x86_64.sh | ||
|
||
wget "https://dockerprovider.blob.core.windows.net/releases/download/4.0.0-0/docker-cimprov-4.0.0-0.universal.x86_64.sh" | ||
wget https://diliprstorage.blob.core.windows.net/mycontainer/docker-cimprov-3.0.0-5.universal.x86_64.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we create a release in github (against health branch) and put the bits there ? please dont ship thru private channels...
ci_feature_prod/setup.sh
Outdated
|
||
#create file to disable omi service startup script | ||
touch /etc/.omi_disable_service_control | ||
|
||
wget "https://github.com/Microsoft/Docker-Provider/releases/download/4.0.0-0/docker-cimprov-4.0.0-0.universal.x86_64.sh" | ||
wget https://diliprstorage.blob.core.windows.net/mycontainer/docker-cimprov-3.0.0-5.universal.x86_64.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we change the version from 3.0.0.5 (which is last released version) to a different version please ?
…nto dilipr/kubeHealth
1. exit if cluster is already onboarded 2. exit if cluster is already opted out of monitoring, but omsagent still runs
…nto dilipr/kubeHealth
kind: Service | ||
apiVersion: v1 | ||
metadata: | ||
name: replicaset-service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A more 'specific' name - so when anyone lists the servcies in the cluster, they can make out that this is for azure monitor containers.
# value: "VALUE_AKS_RESOURCE_ID_VALUE" | ||
#- name: AKS_REGION | ||
# value: "VALUE_AKS_RESOURCE_REGION_VALUE" | ||
- name: AKS_RESOURCE_ID |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are you changing defaults?
value: "my_acs_cluster_name" | ||
#- name: ACS_RESOURCE_NAME | ||
# value: "my_acs_cluster_name" | ||
- name: DISABLE_KUBE_SYSTEM_LOG_COLLECTION |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this has been removed in the last release. This looks like a bad merge...
parameters: | ||
skuName: Standard_LRS | ||
--- | ||
apiVersion: rbac.authorization.k8s.io/v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hope all these things go away as we move away from azure file auto provisioning.
No description provided.