<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anton Antonov on Medium]]></title>
        <description><![CDATA[Stories by Anton Antonov on Medium]]></description>
        <link>https://medium.com/@antoniantonov?source=rss-bd1318263a6d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TDagIjCSGnRovhQ8</url>
            <title>Stories by Anton Antonov on Medium</title>
            <link>https://medium.com/@antoniantonov?source=rss-bd1318263a6d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:24:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@antoniantonov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[K9s — Network Policy Graph (NPG) Read-Only Panel]]></title>
            <link>https://antoniantonov.medium.com/k9s-network-policy-graph-npg-read-only-panel-8141b21922ba?source=rss-bd1318263a6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8141b21922ba</guid>
            <category><![CDATA[kubernetes-network-policy]]></category>
            <category><![CDATA[k9]]></category>
            <category><![CDATA[k9s-for-warriors]]></category>
            <category><![CDATA[kubernetes-networking]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Anton Antonov]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 00:00:16 GMT</pubDate>
            <atom:updated>2026-08-27T00:00:16.964Z</atom:updated>
            <content:encoded><![CDATA[<p>As SecOps and Infra engineer, my day to day duties require a lot of ad hoc work in Kubernetes — EKS, AKS, you name it. Most of our production clusters are quite big, multi-tenant and very heterogenous from tenant to tenant — thus discovery is critical and understanding the network in such a cluster is criticalER.</p><p>This document describes the Network Policy Graph (NPG) read-only panel in K9s that I cooked up on top of my own <a href="https://github.com/antoniantonov/k9s-fork">fork</a> of K9s CLI. That NPG panel allowed me to investigate access and network issues b/n or within different tenants namespaces and pods/deployments.</p><p>I love, LOVE, LOVE K9s CLI and will contribute this panel back to the main fork once I have more confidence it works OK (if the moderators let me, as it has huge amount of changes and code in my fork). I hope you will find it useful as much as I did. If you like what you see and you’d like to contribute — <a href="https://github.com/antoniantonov/k9s-fork">https://github.com/antoniantonov/k9s-fork</a>. I’d love to have you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_fcaK9pfwbeINNiI.png" /></figure><h3>1. What Is Network Policy Graph?</h3><p>Network Policy Graph is a read-only reachability view for standard Kubernetes networking.k8s.io/v1 NetworkPolicy resources. It explains how NetworkPolicy affects traffic to and from a selected workload, called the <strong>subject</strong>.</p><p>NPG is intended to answer questions such as:</p><ul><li>Which ingress sources can reach this workload?</li><li>Which egress destinations can this workload reach?</li><li>Which NetworkPolicy rule contributes to an allow decision?</li><li>Does the policy on the other endpoint also permit the traffic?</li><li>Which ports and protocols remain after both endpoints are evaluated?</li><li>Is a result fully allowed, fully disallowed, only partially allowed, unknown, or based on incomplete data?</li></ul><p>NPG evaluates concrete pod-to-pod paths. For a path to be allowed:</p><ol><li>The source pod’s egress policy must allow it.</li><li>The destination pod’s ingress policy must allow it.</li><li>The two sides must allow at least one common protocol and destination port.</li></ol><p>NetworkPolicy rules are additive allow rules; they are not explicit deny rules. A disallowed result normally means that a pod is isolated in that direction and no matching allow rule permits the peer and port.</p><p>NPG can be opened with:</p><pre>:netpolgraph &lt;kind&gt; &lt;name&gt; [namespace]<br>:npgraph &lt;kind&gt; &lt;name&gt; [namespace]<br>:npg &lt;kind&gt; &lt;name&gt; [namespace]</pre><p>Supported subject kinds are Pod, Deployment, Job, and Namespace. Common aliases such as po, deploy, jobs, and ns are accepted. Examples:</p><pre>:npg pod api-7d8c9f default<br>:npg deployment api default<br>:npg job database-migration default<br>:npg namespace payments</pre><p>The same panel can be opened from a selected Pod, Deployment, Job, or Namespace by pressing Shift-R.</p><p>The panel does not edit, create, or delete NetworkPolicies. It evaluates the current cluster snapshot and provides navigation to related resources and YAML. Opening a resource leaves NPG and pushes the resource view onto the normal K9s breadcrumb stack.</p><p>While NPG is active, the status row beneath the K9s logo shows the NPG-specific read-only graph badge. The badge is removed when NPG stops; it is not a global K9s status.</p><p>NPG evaluates reachability once when opened. Automatic refresh is disabled by default. It can be enabled at a five-second interval with r.</p><p>NPG models the standard Kubernetes NetworkPolicy API, not guaranteed packet delivery. CNI behavior, NAT, hostNetwork, node-local traffic, service meshes, cloud firewalls, vendor-specific policies, application authorization, and other networking layers may change the real result.</p><h3>2. Terminology</h3><h3>Subject</h3><p>The <strong>subject</strong> is the Kubernetes resource whose reachability is being investigated.</p><p>Subject kind Pods evaluated by NPG Pod The selected pod. Deployment The deployment’s current pods. Job The job’s current pods. Namespace The pods in the selected namespace.</p><p>Deployment, Job, and Namespace subjects are aggregates. Their result can therefore include many pod pairs rather than a single connection.</p><h3>Subject kind and primitive kind</h3><p>NPG uses the word <strong>kind</strong> in two related places:</p><ul><li>A <strong>subject kind</strong> identifies what is being investigated: Pod, Deployment, Job, or Namespace.</li><li>A <strong>primitive kind</strong> identifies the peer-side result shown in direction and applicability panels: CIDR, Pod, Namespace, Deployment, or Job.</li></ul><p>The primitive-kind filter is global to the NPG view. It affects both directions and their applicability tables, but it does not change the subject.</p><h3>Primitive</h3><p>A <strong>primitive</strong> is a peer-side reachability target or source:</p><p>Primitive kind Meaning CIDR An ipBlock.cidr, including any except ranges. Pod One concrete pod. Namespace A conservative aggregate of pods in a namespace. Deployment A conservative aggregate of the deployment’s pods. Job A conservative aggregate of the job’s pods.</p><p>For aggregate primitives, Allowed means every evaluated concrete pod pair is allowed. A mix of allowed and non-allowed pairs is Partial, not Allowed.</p><h3>Pod pair</h3><p>A <strong>pod pair</strong> is one concrete source pod and destination pod combination.</p><ul><li>For ingress, the peer pod is the source and the subject pod is the destination.</li><li>For egress, the subject pod is the source and the peer pod is the destination.</li></ul><p>Pair counts are important for aggregate subjects and primitives. For example, two subject pods evaluated against three peer pods can produce six pairs.</p><h3>Ingress</h3><p><strong>Ingress</strong> is traffic entering the subject. The subject is the destination and the displayed primitive is the source.</p><p>An ingress rule:</p><ul><li>selects destination pods through the NetworkPolicy’s podSelector;</li><li>matches sources through the rule’s from peers;</li><li>allows the rule’s destination ports.</li></ul><p>End-to-end ingress reachability also requires the source pod’s egress side to allow compatible traffic.</p><h3>Egress</h3><p><strong>Egress</strong> is traffic leaving the subject. The subject is the source and the displayed primitive is the destination.</p><p>An egress rule:</p><ul><li>selects source pods through the NetworkPolicy’s podSelector;</li><li>matches destinations through the rule’s to peers;</li><li>allows the rule’s destination ports.</li></ul><p>End-to-end egress reachability also requires the destination pod’s ingress side to allow compatible traffic.</p><h3>NetworkPolicy rules</h3><p>A NetworkPolicy rule is one entry in spec.ingress or spec.egress. NPG identifies a real rule by:</p><ul><li>policy namespace and name;</li><li>direction;</li><li>zero-based rule index.</li></ul><p>Rules can match peers with:</p><ul><li>podSelector;</li><li>namespaceSelector;</li><li>both selectors, which form an intersection;</li><li>ipBlock, including except ranges;</li><li>an omitted peer list, which means all peers.</li></ul><p>An omitted port list allows all ports for the protocols represented by the evaluation. Named ports are resolved against destination pod container ports when possible. Ambiguous named ports are reported as unknown rather than being treated as allowed.</p><p>NPG can also display synthetic rules:</p><ul><li><strong>unrestricted</strong>: no NetworkPolicy isolates the pod in that direction;</li><li><strong>default-deny</strong>: a policy isolates the pod, but no additive allow rule permits the evaluated peer and port.</li></ul><p>Synthetic rules explain evaluated behavior but do not correspond to a Kubernetes object.</p><h3>Peer</h3><p>In the Kubernetes API, a <strong>peer</strong> is the opposite endpoint matched by a rule’s from or to entry.</p><p>In the NPG applicability table, <strong>Peer</strong> is an NPG-specific boolean:</p><ul><li>true means the selected rule, or at least one rule in the current direction for an effective table, matched the primitive for at least one concrete pair;</li><li>false means no such current-direction peer match was found;</li><li>n/a means no concrete pair existed, so peer matching was not evaluated.</li></ul><p>Peer=true does not by itself mean that traffic is allowed. The opposite endpoint and port intersection must also permit the traffic.</p><h3>Opposite</h3><p><strong>Opposite</strong> is an NPG-specific concept; it is not a Kubernetes NetworkPolicy field.</p><ul><li>For an ingress row, the opposite side is the source pod’s egress policy.</li><li>For an egress row, the opposite side is the destination pod’s ingress policy.</li></ul><p>The applicability table aggregates this check conservatively:</p><ul><li>true means all concrete pairs represented by the row are effective through the selected/current-direction match and the opposite endpoint permits compatible traffic;</li><li>false means at least one pair lacks a required match, opposite-side allow, or common protocol/port;</li><li>n/a is shown for CIDRs because an address range is not modeled as a pod with an opposite NetworkPolicy side;</li><li>n/a is also shown when no concrete pair exists.</li></ul><pre>flowchart LR<br>    S[Source pod] --&gt; E[&quot;Source egress policy&lt;br/&gt;Peer for an egress row&lt;br/&gt;Opposite for an ingress row&quot;]<br>    E --&gt; P{&quot;Common protocol and&lt;br/&gt;destination port?&quot;}<br>    P --&gt; I[&quot;Destination ingress policy&lt;br/&gt;Opposite for an egress row&lt;br/&gt;Peer for an ingress row&quot;]<br>    I --&gt; D[Destination pod]</pre><p>Always interpret Peer, Opposite, and State together. For example, Peer=true, Opposite=false, and State=Disallowed means that the selected side matched, but the complete end-to-end path was not allowed.</p><h3>Permissions and ports</h3><p>Displayed permissions use values such as:</p><ul><li>TCP/all, UDP/all, or SCTP/all;</li><li>TCP/443;</li><li>TCP/8000-8100;</li><li>TCP/http for a named port that has not been resolved in that context;</li><li>unknown when the exact port cannot be safely determined;</li><li>no ports when there is no effective permission;</li><li>n/a when no concrete pair was evaluated.</li></ul><p>For pod-to-pod traffic, effective permissions are the intersection of the source egress and destination ingress permissions.</p><h3>3. Panels</h3><p>NPG initially shows the Subject panel, both direction panels, and the Details area. Both directions initially use Rules mode, all primitive kinds are enabled, and focus starts on Subject. Neither direction has a selected rule or primitive in either projection. The active Details area therefore starts on Effective Details with Effective Applicability (Ingress). Changing the subject, whether through the picker or Ctrl-S, clears both directions in both projections and returns focus to Subject for the new evaluation.</p><h3>Subject panel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cybH1suMXu5mHUse.png" /></figure><p>The Subject panel identifies the selected subject and lists associated workloads.</p><p>Its summary line contains:</p><ul><li>subject kind and namespace/name;</li><li>number of subject pods;</li><li>whether ingress and egress are visible;</li><li>enabled primitive kinds;</li><li>auto-refresh state;</li><li>truncation, partial-data, loading, and error messages when present.</li></ul><p>The workload table is sorted by namespace and name and is limited to 300 rows. Pod, Deployment, and Job subjects list their resolved pods. Namespace subjects can list Deployments, ReplicaSets, StatefulSets, DaemonSets, Jobs, and Pods.</p><p>Column Meaning Possible values KIND Workload resource kind. Pod, Deployment, ReplicaSet, StatefulSet, DaemonSet, or Job. NAMESPACE Namespace containing the workload. A Kubernetes namespace name. NAME Workload resource name. A Kubernetes resource name. STATUS Compact workload-specific status. Pod phase and readiness, owner information, ready/desired replicas, job condition, or completed count.</p><p>Press y while a workload row is selected to open that workload’s YAML.</p><h3>Ingress and Egress panels</h3><p>Ingress and Egress use the same layout and behavior but represent opposite traffic directions. Press m to switch both panels between Rules and Primitives mode. The mode is always shared, while filters, selections, and scroll positions are preserved independently for each direction and mode. All four direction/projection selection states begin cleared.</p><p>The panel title shows:</p><pre>&lt;Direction&gt; · &lt;Rules|Primitives&gt; · filter: &lt;text&gt;</pre><p>The filter suffix is shown only when that direction and mode has an active text filter.</p><h4>Rules mode</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rxEv2QV462fkiEAA.png" /></figure><p>Rules are rendered as two-line blocks without a header.</p><p>Displayed field Meaning Possible values Rule identity Policy namespace/name and zero-based rule index. Synthetic rows use their synthetic name and index -1. payments/allow-api #0, default-deny #-1, unrestricted #-1. Ports Permissions contributed by the rule. Protocol/all, numeric ports, ranges, named or unknown ports, or no ports. subjects matched/selected Number of subject pods for which the rule contributed evidence divided by the number selected by the policy for that direction. For example, subjects 2/3. peer Compact summary of the rule’s peer selectors. all peers, selector text, CIDR text, default-deny, or unrestricted.</p><p>Rules do not use a separate visible state column. The row color carries the state, and the full state is shown in Rule Details.</p><p>Rule state Meaning Allowed The rule matched all subject pods selected by that rule. Partial The rule matched some, but not all, selected subject pods. Partial Data Warnings indicate that the result was built from incomplete data. [EMPTY] No subject pod was available or no selected subject pod matched the rule. Non-synthetic empty rules are hidden; synthetic explanation rows remain visible.</p><p>Synthetic rows use the normal foreground color instead of an allow/deny color because they are explanations, not real NetworkPolicy rules.</p><p>When a real rule is selected and the direction panel has focus:</p><ul><li>o opens the NetworkPolicy resource;</li><li>y opens its YAML.</li></ul><p>These actions are unavailable for synthetic rules.</p><h4>Primitives mode</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TDGpWlHYHA61F0Q_.png" /></figure><p>Primitives are rendered as two-line blocks with three columns.</p><p>Column or field Meaning Possible values State Aggregate reachability state. Allowed, Disallowed, [PARTIAL allowed/total], Unknown, or Partial Data. Primitive Primitive kind and identity. CIDR, Pod, Namespace, Deployment, or Job plus its name or CIDR. Ports Effective protocol and destination-port permissions. Protocol/all, numeric ports, ranges, named or unknown ports, or no ports. pairs allowed/total Number of definitely allowed concrete pairs divided by all evaluated pairs. For example, pairs 3/4. Explanation Reason for the aggregate state. Examples include all pairs allowed, no matching allow rule, no concrete pairs, or incomplete data.</p><p>Primitive states mean:</p><p>State Meaning Allowed Every concrete pair is allowed. Disallowed Every concrete pair is disallowed. Partial The result is mixed; at least one pair is allowed and at least one is not definitely allowed. Unknown No definitive allow/deny result can be produced. This commonly occurs when there are no current pods to form a pair, or every pair depends on unresolved semantics such as an ambiguous named port. Partial Data The cluster snapshot or pair evaluation is incomplete, so the displayed observations must not be treated as a complete result.</p><p>Press Enter to move from the direction panel to Primitive Details. Press o from the direction panel or Primitive Details to open the selected Pod, Namespace, Deployment, or Job in its native k9s view. Enter from Primitive Details retains the same open behavior. CIDRs are address ranges rather than Kubernetes resources and cannot be opened.</p><h3>Details panel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RpiLmzi3YlKh_cAZ.png" /></figure><p>The Details panel follows the active direction and current selection.</p><h4>Rule Details</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tmZGeI2z5WbYvEtF.png" /></figure><p>When a rule is selected in Rules mode, Rule Details contains:</p><ul><li>direction and subject identity;</li><li>policy namespace, name, and UID;</li><li>zero-based rule index;</li><li>rule state;</li><li>policy pod selector;</li><li>matched/selected subject counts;</li><li>each peer selector or IP block;</li><li>ports;</li><li>rendered rule YAML;</li><li>contributing evidence;</li><li>warnings.</li></ul><p>An Applicability panel is displayed below the rule text.</p><h4>Primitive Details</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cU1JgejRbtyHnX1V.png" /></figure><p>When a primitive is selected in Primitives mode, Primitive Details contains:</p><ul><li>direction and subject identity;</li><li>primitive kind, identity, and UID where applicable;</li><li>state;</li><li>allowed/total pair coverage;</li><li>effective ports;</li><li>explanation;</li><li>policy evidence;</li><li>warnings;</li><li>individual source-to-destination pair decisions.</li></ul><p>A selected primitive has no per-rule applicability table.</p><h4>Effective Details</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nIHIYTxEvM7d48_8.png" /></figure><p>Effective Details is the default on launch and after every subject change. Pressing Esc to clear a later direction selection returns to it. This is the final reachability of every enabled primitive after all rules have been combined, rather than one selected rule’s contribution.</p><p>Effective Details shows:</p><ul><li>direction;</li><li>current Rules or Primitives mode;</li><li>Selection: none;</li><li>enabled primitive kinds;</li><li>total primitive count;</li><li>counts for Allowed, Partial, Disallowed, Unknown, and Partial Data.</li></ul><p>The state counts always add up to the displayed primitive total. Effective Applicability is shown below the text when applicable.</p><h3>Applicability panel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o7q5VzReUf72R9Pq.png" /></figure><p>Applicability explains how a selected rule contributes to each enabled primitive. When no direction row is selected, <strong>Effective Applicability</strong> instead shows the final result after all rules have been applied.</p><p>Column Meaning Possible values Primitive Peer-side primitive being evaluated. CIDR, Pod, Namespace, Deployment, or Job. Peer Whether the current-direction rule or effective rule set matched the primitive. true, false, or n/a. Opposite Whether all represented paths also pass the opposite endpoint’s policy and compatible-port check. true, false, or n/a. CIDRs always use n/a. State End-to-end applicability state for the row. Allowed, Disallowed, Partial, Unknown, or Partial Data. Ports Effective common protocol and destination ports. Protocol/all, numbers, ranges, unknown, no ports, or n/a.</p><p>For a selected rule, State is derived conservatively:</p><ul><li>Allowed: every concrete pair matched the selected rule and is effective end to end;</li><li>Partial: at least one concrete pair is effective through the rule, but not every pair;</li><li>Disallowed: no concrete pair is definitely effective through the selected rule;</li><li>Unknown: no concrete pod pair exists, so the rule’s effect cannot be evaluated;</li><li>Partial Data: the primitive was evaluated from incomplete or truncated data.</li></ul><p>For Effective Applicability, State is the primitive’s final aggregate state after all current-direction and opposite-direction rules are combined.</p><p>An Unknown row is not the same as a denied row. For example, a Deployment primitive with no current pods produces zero concrete pairs. Because no peer selector, opposite endpoint, or port intersection was actually tested, the row uses:</p><pre>Peer: n/a<br>Opposite: n/a<br>State: Unknown<br>Ports: n/a</pre><p>Effective applicability can also be Unknown when concrete pairs exist but all of their decisions are unknown, such as when a named destination port is ambiguous. Partial Data is different: it means the evaluator knows the snapshot is incomplete, for example because of missing RBAC access, a failed resource list/watch, or result truncation.</p><p>The panel uses the globally enabled primitive kinds. Pressing p can therefore add or remove rows from both the direction panels and applicability tables. Pressing a in Rules mode toggles both ingress and egress rule/effective applicability tables between all rows and exact Allowed rows only. Disallowed, Partial, Unknown, and Partial Data rows are hidden. The Allowed-only setting persists across projection changes and applies again when returning to Rules. While active, applicability titles append a second parenthesized suffix (Allowed only), for example Applicability (Ingress) (Allowed only). Allowed-only affects only the visible applicability rows. Effective Details continues to report the complete Allowed, Partial, Disallowed, Unknown, and Partial Data counts, and those counts still sum to the unfiltered primitive total.</p><h3>4. Navigation and Shortcuts</h3><h3>Opening NPG</h3><p>Key or command Action Shift-R Open NPG for the selected Pod, Deployment, Job, or Namespace in its normal resource view. :npg ... Open NPG for an explicitly named subject. :npgraph ... Alias for :npg. :netpolgraph ... Alias for :npg.</p><h3>Focus navigation</h3><p>Tab moves forward and Shift-Tab moves backward through the focus ring. With both directions visible, a selected rule, and applicability rows present, the complete ring is:</p><pre>Subject<br>  -&gt; Ingress<br>  -&gt; Ingress Details<br>  -&gt; Ingress Applicability<br>  -&gt; Egress<br>  -&gt; Egress Details<br>  -&gt; Egress Applicability<br>  -&gt; Subject</pre><p>The reverse order is used by Shift-Tab.</p><p>The ring is dynamic:</p><ul><li>a hidden direction and all of its stops are omitted;</li><li>a selected primitive has Details but no Applicability stop;</li><li>a cleared selection can have Effective Details and Effective Applicability in either mode;</li><li>an empty applicability table is omitted;</li><li>with both directions hidden, only Subject remains in the ring.</li></ul><p>Each direction owns the Details and Applicability stops immediately following it. This lets Tab reach ingress applicability without first moving through the egress panel.</p><p>Key Action Tab Move to the next Subject, direction, Details, or Applicability stop. Shift-Tab Move to the previous focus stop. Left Focus Ingress while focus is outside Details/Applicability. Inside Details/Applicability, the key is passed to the focused widget for scrolling. Right Focus Egress while focus is outside Details/Applicability. Inside Details/Applicability, the key is passed to the focused widget for scrolling.</p><h3>Row navigation</h3><p>The focused table supports:</p><p>Key Action Up / Down Select the previous or next workload, rule, primitive, or applicability row. PageUp / PageDown Move by one visible page. Home / End Move to the first or last row.</p><p>After Esc clears a direction selection, pressing an arrow or paging key in that direction panel restores a selection.</p><h3>Enter behavior</h3><p>Enter is focus-sensitive:</p><p>Current focus Enter action Subject Move to the active visible direction, initially Ingress. Ingress or Egress with a selected rule Move directly to that rule’s Applicability table when it has rows; otherwise move to Rule Details. Ingress or Egress with no selection Move to Effective Applicability when it has rows; otherwise move to Effective Details. Ingress or Egress with a selected primitive Move to Primitive Details. Applicability or Effective Applicability Remain in the applicability table. Use o to open the highlighted Kubernetes primitive. Rule Details No action. Primitive Details Open the selected Pod, Namespace, Deployment, or Job primitive. A CIDR reports that it is not a Kubernetes resource.</p><p>Ctrl-S (<strong>Set As Subject</strong>) promotes the highlighted resource to the current subject and reevaluates:</p><ul><li>In Rules-mode Applicability or Effective Applicability, Pod, Namespace, Deployment, and Job primitives are eligible; CIDRs are not.</li><li>In Subject, selected Pod, Deployment, and Job workload rows are eligible. ReplicaSet, StatefulSet, and DaemonSet rows are not supported subject kinds.</li></ul><p>The new subject begins with both directions and both projections cleared, and focus returns to Subject. Plain Enter never promotes the subject.</p><h3>Open Primitive behavior</h3><p>When the focused selection maps to a native Kubernetes resource, the header shows &lt;o&gt; Open Primitive. Press o to open that resource in its native k9s view from:</p><ul><li>Subject;</li><li>Ingress or Egress in Rules or Primitives mode;</li><li>Applicability or Effective Applicability;</li><li>Primitive Details.</li></ul><p>In Rules mode, a real direction-row selection opens its NetworkPolicy. o is hidden and unbound in Rule Details and whenever the selection is empty, synthetic, unavailable, or a CIDR.</p><h3>Escape behavior</h3><p>Esc has a two-stage behavior for an active ingress or egress selection:</p><ol><li>The first Esc clears that direction’s selection and shows Effective Details and Effective Applicability.</li><li>With no direction selection to clear, Esc performs normal back navigation.</li></ol><p>Esc also cancels NPG dialogs. After opening a resource or YAML view from NPG, Esc returns through the normal breadcrumb stack.</p><h3>Complete NPG key map</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EiL4ZTYWi0QfOxUWkoVERQ.png" /></figure><p>If both directions are hidden, the middle area displays:</p><pre>Both directions are hidden. Press i for ingress or e for egress.</pre><h3>Dialog navigation</h3><p>The Subject picker opened with s supports:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GC_D3r5J_sRdy5AY.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XEYHCEI9pnGe-YHmCmBMNQ.png" /></figure><p>The Primitive Kinds dialog opened with p supports standard form navigation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o6hb5bzi7zL0HA2b.png" /></figure><p>The dialog is sized so all five kind checkboxes and the Apply/Cancel buttons remain visible together on normal terminal sizes, and it is clamped safely to the available space on smaller terminals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rnf3yqVBOWnMdTVhP-wM0Q.png" /></figure><p>The Search dialog opened with / contains Apply, Clear, and Cancel actions. Its target follows focus:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DRH57pMXlDOCADOB.png" /></figure><ul><li>Subject filters the subject workload rows</li><li>Ingress or Egress filters that direction in the current projection</li><li>Rule Details and Applicability filter the current direction’s applicability rows</li><li>Primitive Details filters the current direction’s Primitives panel</li><li>Effective Applicability can be filtered, but Search is hidden while Effective Details text has focus.</li></ul><p>Applicability search matches the values currently displayed in every column. This includes n/a for unevaluated Peer, Opposite, and Ports values, rather than the internal boolean or empty values behind those cells.</p><p>Subject, direction, and applicability filters retain independent state. Esc cancels the dialog and returns focus to the panel that opened it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8141b21922ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>