Update ci cluster #476
Update ci cluster #476
Conversation
hardbyte
force-pushed
the
update-ci-cluster
branch
from
db90690 to
6ed084e
Compare
There was a problem hiding this comment.
These is the most complicated azure pipeline yaml file I ever seen 👍 I have checked the build pipeline on Azure. They all look good to me. So I would like to approve. Just see a warning on Azure: #[warning]All the containers are not in a ready state. If it is not a problem, then I am happy for this branch to be merged.
| command: 'wait' | ||
| arguments: '--namespace $(NAMESPACE) -ldeployment=$(DEPLOYMENT) --timeout=30s --for=condition=Ready pods' | ||
|
|
||
| - task: Kubernetes@1 |
There was a problem hiding this comment.
Just wondering what is the difference between Kubernetes@0 and Kubternetes@1?
There was a problem hiding this comment.
Versions of the task - if there is a Kubernetes@0 I should update it
There was a problem hiding this comment.
Looks like they are fine. If you're interested in the docs have a look here
:-( Perhaps it needs to be split further into templates. I suggest merging so we can rebase the other work and keep developing though. The deployment warning is fine - I've seen that when the redis self test pod doesn't work. |
Now the connection to the Kubernetes cluster uses a configurable Service Connection
hardbyte
force-pushed
the
update-ci-cluster
branch
from
4c147dd to
fa10489
Compare
Refactors most of the Kubernetes related CI testing to use azure's service connections and to migrate to our newer cluster.