apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "22201"
    uid: b44a1255-b2be-419f-8473-b03605e4a22c
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:11:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:50Z"
    - latency: 1.356405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 1.480766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 1.002045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 786.64µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 1.191145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 1.003574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "21590"
    uid: 7f98295f-8600-46a2-9692-34b37cc84442
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:10:50Z"
      message: 'load-balancer-api-external: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.118991ms
      message: 'load-balancer-api-external: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 9.206096ms
      message: 'load-balancer-api-external: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 3.701222ms
      message: 'load-balancer-api-external: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 9.42508ms
      message: 'load-balancer-api-external: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 5.942674ms
      message: 'load-balancer-api-external: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 9.799316ms
      message: 'load-balancer-api-external: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 5.276425ms
      message: 'load-balancer-api-external: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 6.793546ms
      message: 'load-balancer-api-external: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 4.741948ms
      message: 'load-balancer-api-external: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 7.620976ms
      message: 'load-balancer-api-external: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:06:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "21591"
    uid: 98e7ef06-f75a-4553-a6c5-9cf1efa65492
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:10:50Z"
      message: 'load-balancer-api-internal: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.311668ms
      message: 'load-balancer-api-internal: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 9.23892ms
      message: 'load-balancer-api-internal: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 3.672999ms
      message: 'load-balancer-api-internal: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 9.450845ms
      message: 'load-balancer-api-internal: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 5.94882ms
      message: 'load-balancer-api-internal: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 9.866386ms
      message: 'load-balancer-api-internal: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 5.041513ms
      message: 'load-balancer-api-internal: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 6.813578ms
      message: 'load-balancer-api-internal: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 5.3009ms
      message: 'load-balancer-api-internal: tcp connection to a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 7.606256ms
      message: 'load-balancer-api-internal: resolved host name a95151f4cb09943abaf707b7114334e2-5b99a276bd6ac156.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:06:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-129-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "22199"
    uid: 998a5aa8-ec42-4a8f-b5e6-2dfd305ab5b5
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:11:50Z"
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950055ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:50Z"
    - latency: 1.814815ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 1.903089ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 1.953459ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 1.815754ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 2.094371ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 2.071822ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-136-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "22198"
    uid: 9297d715-5335-41f3-86ec-48d952b265ea
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:11:50Z"
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.435µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:50Z"
    - latency: 956.676µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 925.146µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 1.59601ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 1.316494ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 1.361334ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 1.536856ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-138-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "22200"
    uid: 4161eb4d-7116-48e8-af05-6027deab68bf
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:11:50Z"
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.354626ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:50Z"
    - latency: 2.390146ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 2.065232ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 2.31977ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 2.211686ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 2.116509ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 2.32486ms
      message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:04:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: f2395774-bd7e-46fc-9ca6-241c73204c0a
    resourceVersion: "21589"
    uid: 6fe39463-970b-4c80-aa66-f084d411ea41
  spec:
    sourcePod: network-check-source-989f8b8dc-85q4p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:10:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 2.061817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:10:50Z"
    - latency: 958.396µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 2.206493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:09:50Z"
    - latency: 966.884µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 2.027204ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:08:50Z"
    - latency: 984.111µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 1.967318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:07:50Z"
    - latency: 824.92µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:06:50Z"
    - latency: 1.730593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:06:50Z"
kind: List
metadata:
  resourceVersion: ""