Skip to content

MeshService: Ports - we don’t need targetPort, only name, port and appProtocol #2532

MeshService: Ports - we don’t need targetPort, only name, port and appProtocol

MeshService: Ports - we don’t need targetPort, only name, port and appProtocol #2532

Triggered via issue September 16, 2024 14:10
Status Skipped
Total duration 4s
Artifacts

lifecycle.yml

on: issues
lifecycle  /  syncMeta
0s
lifecycle / syncMeta
lifecycle  /  open
0s
lifecycle / open
lifecycle  /  autoclose
0s
lifecycle / autoclose
lifecycle  /  removeAutoclose
0s
lifecycle / removeAutoclose
lifecycle  /  syncFilesFromGithub
0s
lifecycle / syncFilesFromGithub
lifecycle  /  periodicCleanup
0s
lifecycle / periodicCleanup
Fit to window
Zoom out
Zoom in