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

asdf #2

Merged
merged 8 commits into from
Jun 6, 2019
Merged

asdf #2

merged 8 commits into from
Jun 6, 2019

Conversation

justinrlee
Copy link
Owner

We prefer small, well tested pull requests.

Please refer to Contributing to Spinnaker.

When filling out a pull request, please consider the following:

  • Follow the commit message conventions found here.
  • Provide a descriptive summary for your changes.
  • If it fixes a bug or resolves a feature request, be sure to link to that issue.
  • Add inline code comments to changes that might not be obvious.
  • Squash your commits as you keep adding changes.
  • Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.

spinnakerbot and others added 8 commits June 5, 2019 16:15
If a call to kubectl fails to parse the output, we'll return
a parsing failure directly to the user. Instead, return a
failed job with the error message and let the caller handle
the exception as it would any other failed job.
Pods are currently set as having a cluster relationship; this
means that we create a cluster (and associated relationship to
the pod) for every pod in a kubernetes deployment.

This is not necessary, and doesn't match the definition of cluster
used by other providers.  These clusters and relationships are
also not used when we construct the server group model for
a Kubernetes application; we end up ignoring any cluster that
does not map to a server group (which pods do not).

This change will significantly improve the efficiency of both
the caching logic, and the logic to return server groups for
kubernetes (which now will not need to process each pod individually).
@justinrlee justinrlee merged commit 023ca56 into justinrlee:master Jun 6, 2019
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.

5 participants