GitHub
07/03/2023, 4:01 PMGitHub
07/03/2023, 7:05 PMScreenshot 2023-07-03 at 11 45 15 AM▾
Screenshot 2023-07-03 at 11 41 48 AM▾
7/3/2023 6:41:18 PM UTC task submitted to K8s
7/3/2023 6:41:18 PM UTC Unschedulable:0/5 nodes are available: 1 node(s) were unschedulable, 4 node(s) didn't match Pod's node affinity/selector. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling.
7/3/2023 6:42:20 PM UTC [ContainersNotReady|ContainerCreating]: containers with unready status: [aqrp2plhk79cj5dwzg5z-n0-0]|
However this doesn't indicate ongoing node allocation or image pull, two of the most common delays in "happy path" task start up. By comparison kubectl get events
has much richer information.
❯ kubectl get events -n flytesnacks-development --sort-by='{.metadata.creationTimestamp}' --field-selector involvedObject.name=aqrp2plhk79cj5dwzg5z-n0-0
LAST SEEN TYPE REASON OBJECT MESSAGE
6m57s Warning FailedScheduling pod/aqrp2plhk79cj5dwzg5z-n0-0 0/5 nodes are available: 1 node(s) were unschedulable, 4 node(s) didn't match Pod's node affinity/selector. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling.
6m50s Normal TriggeredScaleUp pod/aqrp2plhk79cj5dwzg5z-n0-0 pod triggered scale-up: [{eks-opta-oc-production-nodegroup1-d7fdbb758a882b40-dec46029-5e1e-5bf0-4999-238661b4dc51 0->1 (max: 5)}]
5m55s Normal Scheduled pod/aqrp2plhk79cj5dwzg5z-n0-0 Successfully assigned flytesnacks-development/aqrp2plhk79cj5dwzg5z-n0-0 to ip-10-0-148-239.us-east-2.compute.internal
5m53s Normal Pulling pod/aqrp2plhk79cj5dwzg5z-n0-0 Pulling image "<http://cr.flyte.org/flyteorg/flytekit:py3.9-latest|cr.flyte.org/flyteorg/flytekit:py3.9-latest>"
5m52s Normal TaintManagerEviction pod/aqrp2plhk79cj5dwzg5z-n0-0 Cancelling deletion of Pod flytesnacks-development/aqrp2plhk79cj5dwzg5z-n0-0
5m23s Normal Pulled pod/aqrp2plhk79cj5dwzg5z-n0-0 Successfully pulled image "<http://cr.flyte.org/flyteorg/flytekit:py3.9-latest|cr.flyte.org/flyteorg/flytekit:py3.9-latest>" in 30.158785098s
5m23s Normal Created pod/aqrp2plhk79cj5dwzg5z-n0-0 Created container aqrp2plhk79cj5dwzg5z-n0-0
5m23s Normal Started pod/aqrp2plhk79cj5dwzg5z-n0-0 Started container aqrp2plhk79cj5dwzg5z-n0-0
Goal: What should the final outcome look like, ideally?
The execution closer should include task-specific event details, including scheduling attempts, node allocations, and image pulls.
Describe alternatives you've considered
A more complete solution may overhaul event information in the execution closure so that reasons are not coupled to Flyte state transitions and could instead surface a sink of structured or unstructured event information. This is beyond the scope of this particular issue, but the proposal below does not preclude such an investment in the future.
Propose: Link/Inline OR Additional context
As a potential solution, update DemystifyPending to interleave k8s pod events alongside existing PodCondition reasons.
Note the reporting interface assumes a single-event per state; however, a recent change made it possible to report multiple events using a phase version.
A relatively naive solutions proposed by @hamersaw might be:
• Have propeller keep a watch on k8s events. I assume the kube-client has this functionality. Store these in a local cache (with configurable size) and keyed on the object or Flyte task they are associated with.
• When sending a TaskExecutionEvent we could lookup the k8s events and instead of a singular reason, return a list of reasons (probably update the name) containing all unreported k8s events (use some kind of lastSeen indicator - timestamp, revisionVersion, hash of message, etc).
• Merge the k8s events into the ExecutionClosure.
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteGitHub
07/04/2023, 2:29 PM<https://github.com/flyteorg/flyte/tree/master|master>
by davidmirror-ops
<https://github.com/flyteorg/flyte/commit/4d7b656dae66a75da3480722c3d214ed8ea4f0d1|4d7b656d>
- [RFC] Config Override (#3553)
flyteorg/flyteGitHub
07/04/2023, 2:29 PMGitHub
07/04/2023, 2:56 PMflyte-core
chart with auth
enabled, even with the internal auth server, a user needs to manually:
1. Edit the flyte-admin-secrets
secret and add the oidc_client_secret
2. Edit the flyte-admin-base-config
configmap to add the required information for OIDC
3. Rollout the deployments to make Flyte components aware of the changes
If using an External auth server, more manual edits to the configmap have to be done.
Goal: What should the final outcome look like, ideally?
Similar to how flyte-binary
works, whenever a user enables auth
, they should be able to provide the parameters in the values file and then Helm templates should do the work to update the secret and configmap without user intervention.
Describe alternatives you've considered
None
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteGitHub
07/04/2023, 3:05 PMflyte-binary
chart to K8s environments where they don't have cluster-wide permissions but are more or less constrained to what can be done on a single namespace.
As a way to prepare Flyte for enterprise environments where potential attack surface is a concern and the principle of least privilege is observed, creating a path for single-namespace deployment of Flyte would be useful.
Goal: What should the final outcome look like, ideally?
Make he RBAC to be namespaced, flyte-binary/flytepropeller set to watch a single namespace, and namespace mapping for project/domains fixed to the single namespace
Describe alternatives you've considered
None
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteGitHub
07/04/2023, 11:50 PMGitHub
07/04/2023, 11:53 PMGitHub
07/05/2023, 12:36 AMGitHub
07/05/2023, 3:09 AMGitHub
07/05/2023, 11:38 AM<https://github.com/flyteorg/flytekit/tree/master|master>
by pingsutw
<https://github.com/flyteorg/flytekit/commit/da21782caac8b182489f869f265342d201ed12b9|da21782c>
- Add requirements to imageSpec (#1698)
flyteorg/flytekitGitHub
07/05/2023, 12:28 PMOptional[SomeType] = None
argument in a dynamic
task is a Promise
during execution.
A reproducer:
from typing import Optional
from flytekit import dynamic, workflow
@dynamic
def my_task(opt: Optional[int] = None):
print(opt) # Promise(node:.opt)
@workflow
def workflow():
my_task()
In my_task,
opt
is a Promise(node:.opt).
Works as expected locally but not in a cluster.
Expected behavior
The argument should be None
during execution.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteGitHub
07/05/2023, 12:31 PM<https://github.com/flyteorg/flytepropeller/tree/master|master>
by hamersaw
<https://github.com/flyteorg/flytepropeller/commit/357bf0906d7dc759b0ae36feb5ed6313116ebefd|357bf090>
- Update flyteplugins
(#578)
flyteorg/flytepropellerGitHub
07/05/2023, 12:50 PMScreen Shot 2023-07-05 at 15 41 44▾
GitHub
07/05/2023, 2:23 PMliteral
.
Type
☑︎ Bug Fix
☐ Feature
☐ Plugin
Are all requirements met?
☑︎ Code completed
☐ Smoke tested
☐ Unit tests added
☐ Code documentation added
☑︎ Any pending items have an associated Issue (there aren't any I guess)
Complete description
This came up during internal tests, where it broke existing tests when I changed from a single Literal
to a LiteralMap
in a type transformer with an explicitly set hash value.
Minimal reproducer:
# test.py
from flytekit import Literal
from flytekit.core.local_cache import _recursive_hash_placement
from flytekit.models.literals import LiteralMap, Scalar, Primitive
lit = Literal(
map=LiteralMap(
literals={
"hello": Literal(scalar=Scalar(primitive=Primitive(string_value="hello"))),
}
),
hash="0xffff",
)
if __name__ == "__main__":
print(lit)
# --> prints <FlyteLiteral map { literals { key: "hello" value { scalar { primitive { string_value: "hello" } } } } } hash: "0xffff">
print(_recursive_hash_placement(lit))
# --> prints <FlyteLiteral map { literals { key: "hello" value { scalar { primitive { string_value: "hello" } } } } }>
This means that the _recursive_hash_placement
function, which facilitates part of the hash key computation, silently scrubs hash values from input literal maps, which can cause involuntary cache hits if the values inside the map stay the same.
I would be happy for a discussion - maybe the repro can go in as a unit test in a suitable location.
Tracking Issue
N/A
Follow-up issue
N/A
flyteorg/flytekit
DCO: DCO
✅ 1 other check has passed
1/2 successful checksGitHub
07/05/2023, 2:32 PM--remote
or registering a workflow with pyflyte register to a flyte cluster, no error is reported.
TypeError: Error encountered while executing 'proxy_registration_wf':
Failed to convert outputs of task 'register' at position output:
Python value cannot be None, expected <class 'str'>/<FlyteLiteral simple:
STRING>
Failed with Unknown Exception <class 'TypeError'> Reason: Error encountered while executing 'proxy_registration_wf':
Failed to convert outputs of task 'register' at position output:
Python value cannot be None, expected <class 'str'>/<FlyteLiteral simple: STRING>
Error encountered while executing 'proxy_registration_wf':
Failed to convert outputs of task 'register' at position output:
Python value cannot be None, expected <class 'str'>/<FlyteLiteral simple: STRING>
Expected behavior
either throw an error stating that ContainerTasks are not supported with local pyflyte run execution, or provide support for executing ContainerTasks locally.
Additional context to reproduce
https://gist.github.com/zeryx/b3d4cca7594de252a08ae8a02c2d5d6b
create a WF (or dynamic task) that triggers a ContainerTask
define the ContainerTask to have inputs and outputs
execute an arbitrary step within the ContainerTask (not reading or writing from pipes)
trigger the workflow with pyflyte run
without --remote
Screenshots
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteGitHub
07/05/2023, 2:36 PMGitHub
07/05/2023, 3:11 PM<https://github.com/flyteorg/flyte-conference-talks/tree/main|main>
by cosmicBboy
<https://github.com/flyteorg/flyte-conference-talks/commit/48ea364c963c36400812689911a8bfe1a73146c0|48ea364c>
- update setup requirements
flyteorg/flyte-conference-talksGitHub
07/05/2023, 3:49 PM<https://github.com/flyteorg/flytesnacks/tree/master|master>
by cosmicBboy
<https://github.com/flyteorg/flytesnacks/commit/a49ba5177b72b24601522c42654b91a062f1554d|a49ba517>
- fix formatting, add references (#1014)
flyteorg/flytesnacksGitHub
07/05/2023, 5:00 PM<https://github.com/flyteorg/flytekit/tree/master|master>
by wild-endeavor
<https://github.com/flyteorg/flytekit/commit/7550109d106d4c22689986f32be8d1d3d20d0ef7|7550109d>
- Memory reduction change [ipython] (#1716)
flyteorg/flytekitGitHub
07/05/2023, 5:45 PMGitHub
07/05/2023, 5:49 PMGitHub
07/05/2023, 5:52 PMGitHub
07/05/2023, 6:28 PMarchives.replacements
was deprecated and removed in the latest goreleaser version as per https://goreleaser.com/deprecations/#archivesreplacements. This PR follows the recommendation to use name_template
to get the same effect.
I removed the unused {{ .Arm }}
block also.
Tracking Issue
_Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_
fixes https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/
flyteorg/flytepropeller
GitHub Actions: Goreleaser
GitHub Actions: Build & Push Flytepropeller Image
GitHub Actions: Bump Version
✅ 11 other checks have passed
11/14 successful checksGitHub
07/05/2023, 7:05 PM<https://github.com/flyteorg/flyte-conference-talks/tree/main|main>
by cosmicBboy
<https://github.com/flyteorg/flyte-conference-talks/commit/2d43f0df6b882054b9e4d98b025ff125684f738c|2d43f0df>
- deck url
flyteorg/flyte-conference-talksGitHub
07/05/2023, 7:12 PM<https://github.com/flyteorg/flyte/tree/master|master>
by cosmicBboy
<https://github.com/flyteorg/flyte/commit/37e99676dd5ef19bf2cd06842bfd175f59c58e39|37e99676>
- fix links (#3835)
flyteorg/flyteGitHub
07/05/2023, 7:58 PMGitHub
07/05/2023, 9:00 PMRelease v1.53.0
This is release 1.53.0 (glockenspiel) of gRPC Core.
For gRPC documentation, see grpc.io. For previous releases, see Releases.
This release contains refinements, improvements, and bug fixes, with highlights listed below.
Core
• xDS: fix crash when removing the last endpoint from the last locality in weighted_target. (#32592)
• filter stack: pass peer name up via recv_initial_metadata batch. (#31933)
• [EventEngine] Add advice against blocking work in callbacks. (#32397)
• [http2] Dont drop connections on metadata limit exceeded. (#32309)
• xDS: reject aggregate cluster with empty cluster list. (#32238)
• Fix Python epoll1 Fork Support. (#32196)
• server: introduce ServerMetricRecorder API and move per-call reporting from a C++ interceptor to a C-core filter. (#32106)
• [EventEngine] Add invalid handle types to the public API. (#32202)
• [EventEngine] Refactoring the EventEngine Test Suite: Part 1. (#32127)
• xDS: fix WeightedClusters total weight handling. (#32134)
C++
• Update minimum MSVC version to 2019. (#32615)
• Use CMake variables for paths in pkg-config files. (#31671)
C#
• Grpc.Tools: Use x86 protoc binaries on arm64 Windows. (#32017)
Python
• Support python 3.11 on aarch64. (#32270)
• Include .pyi file. (#32268)
• De-experimentalize wait-for-ready. (#32143)
• De-experimentalize compression. (#32138)
Ruby
• [ruby]: add pre-compiled binaries for ruby 3.2; drop them for ruby 2.6. (#32089)
Release v1.53.0-pre2
This is a prerelease of gRPC Core 1.53.0 (glockenspiel).
For gRPC documentation, see grpc.io. For previous releases, see Releases.... (truncated) Changelog _Sourced from grpcio's changelog._
gRPC Release Schedule
Below is the release schedule for gRPC Java, Go and Core and its dependent languages C++, C#, Objective-C, PHP, Python and Ruby.
Releases are scheduled every six weeks on Tuesdays on a best effort basis. In some unavoidable situations a release may be delayed or released early or a language may skip a release altogether and do the next release to catch up with other languages. See the past releases in the links above. A six-week cycle gives us a good balance between delivering new features/fixes quickly and keeping the release overhead low.
The gRPC release support policy can be found here.
Releases are cut from release branches. For Core and Java repos, the release branch is cut two weeks before the scheduled release date. For Go, the branch is cut just before the release. An RC (release candidate) is published for Core and its dependent languages just after the branch cut. This RC is later promoted to release version if no further changes are made to the release branch. We do our best to keep head of master branch stable at all times regardless of release schedule. Daily build packages from master branch for C#, PHP, Python, Ruby and Protoc plugins are published on packages.grpc.io. If you depend on gRPC in production we recommend to set up your CI system to test the RCs and, if possible, the daily builds.
Names of gRPC releases are here.Commits • `358bfb5` Bump version to 1.53.0 (#32685) • `6e1ebe7` Backport: Ensure compatibility with the new custom kokoro win2019 image (#326... • `44a77f6` Backport 1.53: Update minimum MSVC version to 2019 (#32615) • `c11153c` backport to 1.53: xDS: fix crash when removing the last endpoint from the las... • `7c7712a` Bump version to 1.53.0-pre2. (#32545) • `a4017dc` backport to 1.53: [promises] Make Poll<T> its own type, not a variant<> (#32540) • `3f93c16` Fuzzer fix backport to v1.53 (#32511) • `5b244b2` Bump release version to 1.53.0-pre1 (#32428) • `6589340` Bump core version 202302161703 (#32416) • `d49e151` [backoff] Add random early detection classifier (#32354) • Additional commits viewable in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot r…
flyteorg/flytetools
✅ All checks have passed
2/2 successful checksGitHub
07/05/2023, 9:03 PMRelease 1.53.0
API Changes
• balancer: support injection of per-call metadata from LB policies (#5853)
• resolver: remove deprecated fieldand replace withresolver.Target.Endpoint
(#5852)resolver.Target.Endpoint()
• Special Thanks: `@kylejb`
New Features
• xds/ringhash: introduceenvironment variable to override the maximum ring size. (#5884)GRPC_RING_HASH_CAP
• rls: propagate headers received in RLS response to backends (#5883)
Bug Fixes
• transport: drain client transport when streamID approaches MaxStreamID (#5889)
• server: after GracefulStop, ensure connections are closed when final RPC completes (#5968)
• server: fix a few issues where grpc server uses RST_STREAM for non-HTTP/2 errors (#5893)
• xdsclient: fix race which can happen when multiple load reporting calls are made at the same time. (#5927)
• rls: fix a data race involving the LRU cache (#5925)
• xds: fix panic involving double close of channel in xDS transport (#5959)
• gcp/observability: update method name validation (#5951)
Documentation
• credentials/oauth: markas deprecated (#5882)NewOauthAccess
• Special Thanks: `@buzzsurfr`
Release 1.52.3
Bug Fixes
• Fix user-agent version
Release 1.52.2
Bug Fixes
• xds: fix panic involving double close of channel in xDS transport (#5959)
Release 1.52.1
Bug Fixes
• grpclb: rename grpclbstate package back to state (#5963)
Release 1.52.0
New Features
• xdsclient: log node ID with verbosity INFO (#5860)
• ringhash: impose cap onto reduce possibility of OOMs (#5801)max_ring_size
Behavior Changes... (truncated) Commits • `dba26e1` Change version to 1.53.0 (#5983) • `2a1e934` server: after GracefulStop, ensure connections are closed when final RPC comp... • `e2d69aa` tests: fix spelling of variable (#5966) • `a6376c9` xds/resolver: cleanup tests to use real xDS client 3/n (#5953) • `bf8fc46` xds/resolver: cleanup tests to use real xDS client 5/n (#5955) • `3930549` resolver: replace resolver.Target.Endpoint field with Endpoint() method (#5852) • `894816c` grpclb: rename
grpclbstate
package back to state
(#5962)
• `e5a0237` encoding: fix duplicate compressor names (#5958)
• `4adb2a7` xds/resolver: cleanup tests to use real xDS client 2/n (#5952)
• `52a8392` gcp/observability: update method name validation (#5951)
• Additional commits viewable in compare view
Dependabot compatibility score
You can trigger a rebase of this PR by commenting @dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
Note > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.flyteorg/flyteadmin GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 8 other checks have passed 8/12 successful checks
GitHub
07/05/2023, 9:22 PMRelease 1.53.0
API Changes
• balancer: support injection of per-call metadata from LB policies (#5853)
• resolver: remove deprecated fieldand replace withresolver.Target.Endpoint
(#5852)resolver.Target.Endpoint()
• Special Thanks: `@kylejb`
New Features
• xds/ringhash: introduceenvironment variable to override the maximum ring size. (#5884)GRPC_RING_HASH_CAP
• rls: propagate headers received in RLS response to backends (#5883)
Bug Fixes
• transport: drain client transport when streamID approaches MaxStreamID (#5889)
• server: after GracefulStop, ensure connections are closed when final RPC completes (#5968)
• server: fix a few issues where grpc server uses RST_STREAM for non-HTTP/2 errors (#5893)
• xdsclient: fix race which can happen when multiple load reporting calls are made at the same time. (#5927)
• rls: fix a data race involving the LRU cache (#5925)
• xds: fix panic involving double close of channel in xDS transport (#5959)
• gcp/observability: update method name validation (#5951)
Documentation
• credentials/oauth: markas deprecated (#5882)NewOauthAccess
• Special Thanks: `@buzzsurfr`
Release 1.52.3
Bug Fixes
• Fix user-agent version
Release 1.52.2
Bug Fixes
• xds: fix panic involving double close of channel in xDS transport (#5959)
Release 1.52.1
Bug Fixes
• grpclb: rename grpclbstate package back to state (#5963)
Release 1.52.0
New Features
• xdsclient: log node ID with verbosity INFO (#5860)
• ringhash: impose cap onto reduce possibility of OOMs (#5801)max_ring_size
Behavior Changes... (truncated) Commits • `dba26e1` Change version to 1.53.0 (#5983) • `2a1e934` server: after GracefulStop, ensure connections are closed when final RPC comp... • `e2d69aa` tests: fix spelling of variable (#5966) • `a6376c9` xds/resolver: cleanup tests to use real xDS client 3/n (#5953) • `bf8fc46` xds/resolver: cleanup tests to use real xDS client 5/n (#5955) • `3930549` resolver: replace resolver.Target.Endpoint field with Endpoint() method (#5852) • `894816c` grpclb: rename
grpclbstate
package back to state
(#5962)
• `e5a0237` encoding: fix duplicate compressor names (#5958)
• `4adb2a7` xds/resolver: cleanup tests to use real xDS client 2/n (#5952)
• `52a8392` gcp/observability: update method name validation (#5951)
• Additional commits viewable in compare view
Dependabot compatibility score
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
flyteorg/flyteadmin
GitHub Actions: Build & Push Flytescheduler Image
GitHub Actions: Build & Push Flyteadmin Image
GitHub Actions: Goreleaser
GitHub Actions: Bump Version
GitHub Actions: End2End Test / End to End tests
✅ 9 other checks have passed
9/14 successful checks