Skip to content

History

Revisions

  • Add FAQ page

    @minhtule minhtule committed Aug 24, 2026
    9703051
  • Removed V2 pre-release note

    @ekampf ekampf committed Aug 12, 2026
    72f0d71
  • Update

    @minhtule minhtule committed Aug 11, 2026
    e49fbad
  • Update

    @minhtule minhtule committed Aug 11, 2026
    54729c0
  • Update

    @minhtule minhtule committed Aug 10, 2026
    0d1ce8b
  • Update

    @minhtule minhtule committed Aug 9, 2026
    6fe2f90
  • Update

    @minhtule minhtule committed Aug 9, 2026
    ff6f3db
  • Update

    @minhtule minhtule committed Aug 9, 2026
    30bad0d
  • Update

    @minhtule minhtule committed Aug 9, 2026
    6d2589b
  • Update migration v1 to v2

    @minhtule minhtule committed Aug 9, 2026
    4ad9dc8
  • Updated _Sidebar (markdown)

    @ekampf ekampf committed Jul 27, 2026
    4221a38
  • Updated Guide Identity Firewall (markdown)

    @ekampf ekampf committed Jul 27, 2026
    23fef35
  • Updated Guide Resource Management (markdown)

    @ekampf ekampf committed Jul 27, 2026
    b08fb0e
  • Updated Guide Connector (markdown)

    @ekampf ekampf committed Jul 27, 2026
    221cae2
  • Correct namespace resolution timing, split out gatewayRef re-declaration The resourceRef fallback to `default` lived in the operator, not the CRD schema, so resolution changes when the v2 operator is deployed; groupRef needs both the new CRDs and the v2 operator. Also promote re-declaring hand-authored Kubernetes resources to its own step, and turn the annotation mapping into a table.

    @minhtule minhtule committed Jul 27, 2026
    a62d7d5
  • Document v2 namespace resolution for object references * Regenerate API Reference: object-reference `namespace` now defaults to the declaring object's own namespace, plus `remoteNetworkId` on Connector/Resource * Drop `namespace: default` from the `TwingateResourceAccess` examples * Note that removing an explicit `namespace: default` from an existing object trips the `resourceRef`/`groupRef` immutability rules * Clarify that applying the new CRDs is part of every upgrade, and that the Kubernetes API interruption covers hand-authored resources too

    @minhtule minhtule committed Jul 25, 2026
    b97f2b0
  • Annotate step 1 and step 4 values.yaml examples with migration callouts

    @minhtule minhtule committed Jul 24, 2026
    056f62b
  • Format proxy-removal changes as bullets, drop Gateway-wiki migration links

    @minhtule minhtule committed Jul 24, 2026
    4574e2e
  • Document gateway subchart values restructure in v1-to-v2 migration Explain the move from annotation-based twingate.resource.extraAnnotations to twingateOperator.gateway/kubernetesResource fields, with a before/after values.yaml in the upgrade path.

    @minhtule minhtule committed Jul 23, 2026
    b5871df
  • Clarify migration scope and add Kubernetes access warning - Note that renaming Service annotations is the whole migration for most users - Gate the upgrade path to gateway subchart / Kubernetes resource users - Warn that Kubernetes API access is interrupted during the migration - Fold the CRD caution into step 3 to drop a redundant callout

    @minhtule minhtule committed Jul 23, 2026
    670576e
  • Regenerate API Reference for Gateway / Identity Firewall CRDs Adds TwingateGateway and TwingateCertificateAuthority, the WebApp resource type, gatewayRef, and upstream/downstream/requestHeaderRewrites; drops the removed proxy field.

    @minhtule minhtule committed Jul 23, 2026
    7b1c4f6
  • Restructure wiki around Gateway / Identity Firewall - Split User-Guide into Guide-Connector and Guide-Resource-Management - Add Guide-Identity-Firewall (Gateway setup, Kubernetes and Web App resources) - Add Migration-v1-to-v2 guide - Nest guides under "User Guides" in the sidebar; update Getting-Started link

    @minhtule minhtule committed Jul 23, 2026
    cc6ed19
  • Updated API Reference (markdown)

    @ekampf ekampf committed May 19, 2026
    dab3c08
  • Added example re production Connector deployment

    @ekampf ekampf committed Apr 20, 2026
    112fae4
  • Revert "Add protocol/port restriction annotation docs to User Guide" This reverts commit b4ae35b03669ce464e446b4e2d12d15567b75216.

    @romankor romankor committed Apr 10, 2026
    92440ee
  • Add protocol/port restriction annotation docs to User Guide

    @romankor romankor committed Apr 10, 2026
    b4ae35b
  • Generated sidebar with github-wiki-sidebar

    @ekampf ekampf committed Sep 5, 2025
    6eae165
  • undo

    @ekampf ekampf committed Sep 5, 2025
    64807a6
  • test frontmatter

    @ekampf ekampf committed Sep 5, 2025
    2b80958
  • Destroyed # Known Issues and Limitations (markdown)

    @minhtule minhtule committed Jun 29, 2025
    bed648f