Skip to content
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

fix(platform): test e2e failed #1477

Merged
merged 1 commit into from
Aug 13, 2021
Merged

Conversation

TomatoAres
Copy link
Contributor

@TomatoAres TomatoAres commented Aug 12, 2021

add namespace in kube config

What type of PR is this?

/kind bug
/kind failing-test

What this PR does / why we need it:

Without this pr:

  1. platfomClient in tke-platform-controller will be nil
  2. tke-platform-api pod will resolve tke-platformapi service with pod ip ranther than service ip
  3. validating can not skip checking spec.version with global cluster

@TomatoAres TomatoAres changed the title fix(platform): for test fix(platform): fix test e2e failed Aug 12, 2021
@TomatoAres TomatoAres changed the title fix(platform): fix test e2e failed fix(platform): test e2e failed Aug 12, 2021
@@ -166,6 +167,7 @@ func NewProvider() (*Provider, error) {

containerregistry.Init(cfg.Registry.Domain, cfg.Registry.Namespace)

log.Infof("cfg:%#v\n", cfg)
Copy link
Contributor

Choose a reason for hiding this comment

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

why print these 2 logs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because these config is import, and nowhere print in log.

1. add platformAPIClientConfig
2. add namespace in tke-platform-api
3. modify validate spec logic
@leoryu leoryu merged commit 083b789 into tkestack:master Aug 13, 2021
@TomatoAres TomatoAres deleted the fix-e2e-3 branch August 13, 2021 03:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants