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

Flyte-core add missing podEnv values #4807

Merged
merged 2 commits into from
Feb 6, 2024

Conversation

ddl-ebrown
Copy link
Contributor

@ddl-ebrown ddl-ebrown commented Jan 31, 2024

Tracking issue

https://github.com/flyteorg/flyte/issues/

Why are the changes needed?

What changes were proposed in this pull request?

How was this patch tested?

Setup process

Screenshots

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Related PRs

Docs link

 - In flyteorg#4756 / fb9ffd5, flyte-core got
   consistent podEnv values established in values.yaml. However, these
   values were not properly injected into *all* the containers being
   used in various deployments.

   Fix that so that they are used in all deployments

Signed-off-by: ddl-ebrown <[email protected]>
 - Some linters consider empty env: as invalid k8s YAML, because env is
   typically an [] when no values are set

   Prevent rendering the console env block without values

Signed-off-by: ddl-ebrown <[email protected]>
@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. bug Something isn't working labels Jan 31, 2024
Copy link

codecov bot commented Feb 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2794894) 58.98% compared to head (232c240) 59.12%.
Report is 4 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4807      +/-   ##
==========================================
+ Coverage   58.98%   59.12%   +0.14%     
==========================================
  Files         644      644              
  Lines       55145    52788    -2357     
==========================================
- Hits        32527    31213    -1314     
+ Misses      20046    19001    -1045     
- Partials     2572     2574       +2     
Flag Coverage Δ
unittests 58.51% <ø> (-0.48%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@davidmirror-ops davidmirror-ops left a comment

Choose a reason for hiding this comment

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

So did you find this out by deploying with podEnvs correct?
Thanks!

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Feb 5, 2024
@ddl-ebrown
Copy link
Contributor Author

Correct. We have some checks in our deployments that set podEnv at the Helmfile level then make sure those values propagate to all the pods properly. These containers were the ones that failed the checks

@davidmirror-ops
Copy link
Contributor

@ddl-ebrown for the failing check, you should rebase onto master.

@pingsutw pingsutw merged commit b7d8492 into flyteorg:master Feb 6, 2024
50 of 51 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working lgtm This PR has been approved by a maintainer size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants