apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14667"
    uid: e85acd02-bcac-4986-815e-a0dad0652b78
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:55:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:55:41Z"
    - latency: 1.204028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 961.394µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 960.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 1.035241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 1.023509ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 1.578118ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14338"
    uid: f8d8587d-a518-4607-9be9-6b8759117407
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:54:41Z"
      message: 'load-balancer-api-external: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.255812ms
      message: 'load-balancer-api-external: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 6.42648ms
      message: 'load-balancer-api-external: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 4.576472ms
      message: 'load-balancer-api-external: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 9.612189ms
      message: 'load-balancer-api-external: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 5.877715ms
      message: 'load-balancer-api-external: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 6.530279ms
      message: 'load-balancer-api-external: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 6.085253ms
      message: 'load-balancer-api-external: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 6.395937ms
      message: 'load-balancer-api-external: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 5.978557ms
      message: 'load-balancer-api-external: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 6.449294ms
      message: 'load-balancer-api-external: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:50:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14339"
    uid: df071ec1-cc56-47bb-b41b-edc5e444e3ac
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:54:41Z"
      message: 'load-balancer-api-internal: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.009006ms
      message: 'load-balancer-api-internal: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 6.50252ms
      message: 'load-balancer-api-internal: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 4.613941ms
      message: 'load-balancer-api-internal: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 9.588793ms
      message: 'load-balancer-api-internal: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 5.863299ms
      message: 'load-balancer-api-internal: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 6.54094ms
      message: 'load-balancer-api-internal: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 6.077601ms
      message: 'load-balancer-api-internal: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 6.302851ms
      message: 'load-balancer-api-internal: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 5.996247ms
      message: 'load-balancer-api-internal: tcp connection to a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 6.372121ms
      message: 'load-balancer-api-internal: resolved host name a824b7401b6234636a3abbe2de996087-014b9c954fa662b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:50:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-network-check-target-ip-10-0-128-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14664"
    uid: 6647fae6-6952-4a60-9df4-a319f56ad737
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:55:41Z"
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.109µs
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:55:41Z"
    - latency: 1.033543ms
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 751.505µs
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 1.197789ms
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 911.764µs
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 1.365388ms
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 1.034054ms
      message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-network-check-target-ip-10-0-133-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14666"
    uid: 63dd5d85-4a2f-43c4-8649-b729ea57cabf
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:55:41Z"
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.761632ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:55:41Z"
    - latency: 2.267268ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 2.212198ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 2.360889ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 2.550035ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 2.219294ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 2.379107ms
      message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-network-check-target-ip-10-0-142-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14665"
    uid: 4ef62a19-5bc1-4c83-9b23-9363f5e7c1b6
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:55:41Z"
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.589321ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:55:41Z"
    - latency: 2.123527ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 2.060663ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 2.470465ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 2.254274ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 2.523047ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 2.165712ms
      message: 'network-check-target-ip-10-0-142-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:48:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-231.ec2.internal
      uid: 3d48ef5a-8e2b-458f-af04-266d22d112e4
    resourceVersion: "14337"
    uid: c88dc955-4d5c-40d0-825c-80acdcdb75ad
  spec:
    sourcePod: network-check-source-56d84b9f44-m9gp6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:54:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 1.679218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:54:41Z"
    - latency: 935.084µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 1.700584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:53:41Z"
    - latency: 861.211µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 1.620446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:52:41Z"
    - latency: 1.279331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 1.681079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:51:41Z"
    - latency: 1.000487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:41Z"
    - latency: 1.712033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:50:41Z"
kind: List
metadata:
  resourceVersion: ""