Documentation already contains drasi env kube command - no changes needed

[Copilot]

Issue describes missing drasi env kube instructions in installation guides, but investigation shows all Kubernetes installation guides already include this command with proper documentation.

Current State

All five Kubernetes installation guides contain drasi env kube before drasi init:

• install-on-kind, install-on-aks, install-on-eks, install-on-k3s: Added August 2025 (PR Added instructions for running drasi env kube before running drasi init #129)
• install-using-manifests: Included since creation July 2025 (PR CLI: init manifest flag docs #140)
• install-on-docker: Correctly omits command (Docker mode doesn't use Kubernetes contexts)

Each guide includes this section before installation:

Before installing Drasi, ensure that your kubectl context is set to the cluster where you want to install Drasi. Then, configure a new Drasi CLI environment by running the following command:
```text
drasi env kube

This command adds the current Kubernetes context as a Drasi configuration and set it as the current Drasi environment.

## Resolution

Issue appears to be outdated. No documentation changes required.

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>


----

*This section details on the original issue you should resolve*

<issue_title>Add `drasi env kube` command to our tutorials and installation guides</issue_title>
<issue_description>Currently, we do not have any instructions on running the correct `drasi env` command in our installation guides. This will result in an error being thrown when we tried to install Drasi, as the current Drasi context is not set. 

We should add a section in each of installation guide to highlight this requirement.</issue_description>

<agent_instructions># ===================================================================
# DRASI AUTHORITATIVE CONTEXT
# Purpose: Single source of truth for all terminology, concepts, phrasing, 
#          components, features, and positioning when AI agents generate code, 
#          docs, blog posts, or answers about Drasi.
# Version: 0.1.0
# Updated: 2025-12-04
# ===================================================================

project:
  name: Drasi
  one_liner: "Drasi is an open-source Data Change Processing platform that simplifies the creation and operation of change-driven solutions."
  website: https://drasi.io
  repo: https://github.com/drasi-project/drasi-platform
  license: Apache 2.0
  current_stable_version: early-release
  development_stage: CNCF Sandbox

audience:
  primary: |
    Solution architects, software developers, and DevOps engineers building change-driven solutions in cloud-native, IoT, 
    or enterprise environments.
  secondary: "Open-source contributors, and CNCF members."

mission:
  purpose: |
    Drasi enables change-driven architectures—a specialized subset of event-driven architecture—by providing declarative 
    continuous queries to monitor data sources, isolate semantic changes, and trigger precise reactions, eliminating the 
    overhead of parsing, filtering, and state management in generic event streams.
  problem_it_solves: |
    Detecting specific meaningful changes in data is complex.
    Polling datasources to retrieve current data and compare it with the last poll results is inefficient and requires complex
    logic to isolate what has changed.
    Processing change feeds generated by datasources can require significant infrastructure to deal with high volumes of mostly
    uninteresting change events. Filtering to just the relevant events and determining what has changed can require complex logic
    and cache state management.
  non_goals:
    - "Generic event streaming or arbitrary payload processing (e.g., like Kafka)"
    - "Static, one-time queries (Drasi focuses on perpetual, change-aware monitoring)"
    - "Change Data Capture (CDC) for data replication"

key_phrases:
  always_say:
    - "Drasi is an open-source Data Change Processing platform."
    - "Drasi simplifies the creation and operation of change-driven solutions."
    - "Drasi enables change-driven architectures."
    - "Drasi uses declarative continuous queries to isolate meaningful data changes."
    - "Drasi avoids the overhead of polling, parsing, filtering, and state management."
  never_say:
    - "Drasi is an event-driven platform"  # Focus on change-driven, not generic events
    - "Drasi is used to build event-driven architectures or solutions"  # Focus on change-driven architectures
    - "Drasi is a streaming platform"  # Focus on change semantics, not generic
    - "Drasi is for stream processing"  # Focus on change-driven solutions

core_concepts:
  - term: Change
    definition: "A set of additions, updates, and/or deletions to a continuous query result set occurring because of changes to the source data; has precise semantics defined by the author of the query, not the source system."
    aliases: [delta, transition]
    forbidden_terms: [event, signal]
  - term: Continuous Query
    definition: "A query written in openCypher or GQL that runs perpetually, fed by change logs from one or more data sources, maintaining the current set of query results and generating change notifications when those results change due to data modifications."
    aliases: [cq, perpetual query]
    forbidden_terms: [static query, poll]
  - term: Reaction
    definition: "A action triggered in response to a precise change (add/update/delete) in a continuous query's result set, enabling clear state transitions like entering or exiting conditions."
    aliases: [handler, action]
    forbidden_terms: [listener, subscriber]
  - term: Source
    definition: "Data repository (e.g., databases, Kubernetes, monitoring tools) that provides a source of change for Continuous Queries."
    aliases: [connector, feed]
    forbidden_terms: [stream, topic]
  - term: Change-Driven Solution
    definition: "Systems that do something in response to a meaningful change or the absence of change in relevant data."
    aliases: [CDS]
    forbidden_terms: [generic event-driven]
  - term: Change-Driven Architecture
    definition: "An architectural style focused on detecting and reacting to specific, meani...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes drasi-project/docs#126

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs.