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.

Sign up for GitHub

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

Jump to bottom

When using Istio no mesh ReplicaSet Failures are still not being propagated #14621

Closed
gabo1208 opened this issue Nov 15, 2023 · 2 comments
Closed

When using Istio no mesh ReplicaSet Failures are still not being propagated #14621

gabo1208 opened this issue Nov 15, 2023 · 2 comments
Assignees
@gabo1208
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@gabo1208
Copy link
Member

gabo1208 commented Nov 15, 2023 •
edited
Loading

What version of Knative?

all

Expected Behavior

After #14453 when a Replicaset fails, the Knative Service should fail fast and tell the user what is happening (from the Deployment Status)

Actual Behavior

When using Istio with the no-mesh option, the ReplicaSet Failure is not propagated and is acting as it was before, waiting for a ProgressDeadline error

Steps to Reproduce the Problem

Configure Istio no mesh setup and run TestResourceQuotaError
@gabo1208 gabo1208 added the kind/bug Categorizes issue or PR as related to a bug. label Nov 15, 2023
@gabo1208 gabo1208 changed the title Istio no mesh not propagating ReplicaSet Failures When using Istio no mesh ReplicaSet Failures are still not being propagated Nov 15, 2023
@gabo1208 gabo1208 mentioned this issue Nov 15, 2023
Merged
@dprotaso
Copy link
Member

/assign @gabo1208

@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gabo1208 gabo1208

Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dprotaso @gabo1208