Skip to content

Conversation

@ColdsteelRail
Copy link
Member

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

  • N
  • Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

  • N
  • Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

  • Unit test
  • Integration test
  • Benchmark (add benchmark stats below)
  • Manual test (add detailed scripts or steps below)
  • Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@codecov
Copy link

codecov bot commented Aug 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.04%. Comparing base (d0e6766) to head (6a15721).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #239      +/-   ##
==========================================
+ Coverage   65.95%   66.04%   +0.08%     
==========================================
  Files          78       78              
  Lines        5514     5513       -1     
==========================================
+ Hits         3637     3641       +4     
+ Misses       1520     1518       -2     
+ Partials      357      354       -3     
Flag Coverage Δ
unittests 66.04% <100.00%> (+0.08%) ⬆️

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.

@ColdsteelRail ColdsteelRail changed the title continue to finish lifecycle if job finished add finalizer for origin pod in operationjob replace Aug 5, 2024
@ColdsteelRail ColdsteelRail changed the title add finalizer for origin pod in operationjob replace improve replace: add finalizer for origin pod, improve list new pod, add some events Aug 5, 2024
@ColdsteelRail ColdsteelRail requested a review from wu8685 August 5, 2024 13:16
logger := r.Logger.WithValues("operationjob", req.String())
instance := &appsv1alpha1.OperationJob{}
if err := r.Client.Get(ctx, req.NamespacedName, instance); err != nil {
err := r.Client.Get(ctx, req.NamespacedName, instance)
Copy link
Collaborator

Choose a reason for hiding this comment

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

What is this change for?

Copy link
Collaborator

@wu8685 wu8685 left a comment

Choose a reason for hiding this comment

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

lgtm

@wu8685 wu8685 merged commit ccae59b into main Aug 5, 2024
@wu8685 wu8685 deleted the operationJob-replace branch August 5, 2024 13:44
@github-actions github-actions bot locked and limited conversation to collaborators Aug 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

提供灰度流量的能力

3 participants