Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

k8s: v1.5.1 -> v1.5.2 #189

Closed
wants to merge 3 commits into from

Conversation

colemickens
Copy link
Contributor

No description provided.

@msftclas
Copy link

Hi @colemickens, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!


It looks like you're a Microsoft contributor (Cole Mickens). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Copy link
Contributor

@anhowe anhowe left a comment

Choose a reason for hiding this comment

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

lgtm. Also, please confirm if the dashboard was bumped?

@colemickens
Copy link
Contributor Author

Yes. I checked. No new release: https://github.com/kubernetes/dashboard/releases

@colemickens colemickens force-pushed the colemickens-k8s-1.5.2 branch 2 times, most recently from 167b11a to 061eb1e Compare January 19, 2017 18:40
@colemickens
Copy link
Contributor Author

This now features ACR integration enablement, though this likely won't work until 1.5.3 due to this: kubernetes/kubernetes#40142

@colemickens colemickens force-pushed the colemickens-k8s-1.5.2 branch from 061eb1e to 6498d53 Compare January 23, 2017 20:43
Copy link
Contributor

@anhowe anhowe left a comment

Choose a reason for hiding this comment

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

adding a block in, since there are issues with 1.5.2 and ACR

@colemickens colemickens self-assigned this Jan 25, 2017
@colemickens colemickens deleted the colemickens-k8s-1.5.2 branch February 21, 2017 22:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants