apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "14733"
    uid: 7f8eddb3-24a6-412b-aa95-a88f42f8839f
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:13Z"
    - latency: 1.594954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:13Z"
    - latency: 984.571µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:13Z"
    - latency: 1.455668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:13Z"
    - latency: 1.412017ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:13Z"
    - latency: 1.080266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:13Z"
    - latency: 1.231564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "17720"
    uid: 59dbac3f-6037-4ed5-b9e2-ff859346da3c
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:01:13Z"
      message: 'load-balancer-api-external: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.450653ms
      message: 'load-balancer-api-external: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:07:13Z"
    - latency: 8.806301ms
      message: 'load-balancer-api-external: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:07:13Z"
    - latency: 4.062122ms
      message: 'load-balancer-api-external: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:06:13Z"
    - latency: 7.926042ms
      message: 'load-balancer-api-external: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:06:13Z"
    - latency: 5.198486ms
      message: 'load-balancer-api-external: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:05:13Z"
    - latency: 8.862523ms
      message: 'load-balancer-api-external: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:05:13Z"
    - latency: 5.389586ms
      message: 'load-balancer-api-external: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:04:13Z"
    - latency: 7.101426ms
      message: 'load-balancer-api-external: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:04:13Z"
    - latency: 5.031214ms
      message: 'load-balancer-api-external: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:13Z"
    - latency: 7.179585ms
      message: 'load-balancer-api-external: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:03:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "17721"
    uid: ca348275-e59d-46a4-a9a5-b0e620364831
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:01:13Z"
      message: 'load-balancer-api-internal: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.521069ms
      message: 'load-balancer-api-internal: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:07:13Z"
    - latency: 8.764898ms
      message: 'load-balancer-api-internal: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:07:13Z"
    - latency: 4.062623ms
      message: 'load-balancer-api-internal: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:06:13Z"
    - latency: 7.840757ms
      message: 'load-balancer-api-internal: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:06:13Z"
    - latency: 5.17134ms
      message: 'load-balancer-api-internal: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:05:13Z"
    - latency: 8.947233ms
      message: 'load-balancer-api-internal: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:05:13Z"
    - latency: 5.038042ms
      message: 'load-balancer-api-internal: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:04:13Z"
    - latency: 7.154231ms
      message: 'load-balancer-api-internal: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:04:13Z"
    - latency: 5.039762ms
      message: 'load-balancer-api-internal: tcp connection to a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:13Z"
    - latency: 7.212828ms
      message: 'load-balancer-api-internal: resolved host name a3b22aa768b324deca48e981c10d909d-60cb925e3fcb72ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:03:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-network-check-target-ip-10-0-135-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "14729"
    uid: 26bdaab9-f9b4-417d-912c-eaa03334a7ef
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:13Z"
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 766.315µs
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:13Z"
    - latency: 994.967µs
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:13Z"
    - latency: 782.165µs
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:13Z"
    - latency: 769.034µs
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:13Z"
    - latency: 957.691µs
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:13Z"
    - latency: 1.189882ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:13Z"
    - latency: 1.815885ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-network-check-target-ip-10-0-136-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "14730"
    uid: b6c7ae7f-5792-4349-b700-1ecaa6c4d690
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:13Z"
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.065852ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:13Z"
    - latency: 2.266141ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:13Z"
    - latency: 1.672162ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:13Z"
    - latency: 2.148834ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:13Z"
    - latency: 1.787044ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:13Z"
    - latency: 1.891752ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:13Z"
    - latency: 1.700303ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-network-check-target-ip-10-0-137-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "14731"
    uid: ab7a2afe-ab14-4183-8a03-d0dd9a9f1372
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:13Z"
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.575255ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:13Z"
    - latency: 2.304017ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:13Z"
    - latency: 2.311161ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:13Z"
    - latency: 2.033493ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:13Z"
    - latency: 2.160869ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:13Z"
    - latency: 2.012916ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:13Z"
    - latency: 2.229854ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-178.ec2.internal
      uid: 688c6161-8401-4c4b-8951-c0d3db5fa58d
    resourceVersion: "17718"
    uid: e52d3197-6791-4bc2-9c2d-00481980d95f
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjvzw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:01:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.625µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:07:13Z"
    - latency: 1.682759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:07:13Z"
    - latency: 998.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:06:13Z"
    - latency: 1.626377ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:06:13Z"
    - latency: 941.461µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:05:13Z"
    - latency: 1.878398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:05:13Z"
    - latency: 747.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:04:13Z"
    - latency: 2.004727ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:04:13Z"
    - latency: 801.897µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:13Z"
    - latency: 1.688524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:03:13Z"
kind: List
metadata:
  resourceVersion: ""