Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Administration Guide

    Home FortiManager 6.4.2 Administration Guide
    6.4.2
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.8
    7.2.7
    7.2.6
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.13
    7.0.12
    7.0.11
    7.0.10
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.15
    6.4.14
    6.4.13
    6.4.12
    6.4.11
    6.4.10
    6.4.9
    6.4.8
    6.4.7
    6.4.6
    6.4.5
    6.4.4
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.2.13
    6.2.12
    6.2.11
    6.2.10
    6.2.9
    6.2.8
    6.2.7
    6.2.6
    6.2.6
    6.2.5
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.0.12
    6.0.11
    6.0.10
    6.0.9
    6.0.8
    6.0.7
    6.0.6
    6.0.5
    6.0.4
    6.0.3
    6.0.2
    6.0.1
    6.0.0
    5.6.11
    5.6.10
    5.6.9
    5.6.8
    5.6.7
    5.6.6
    5.6.5
    5.6.4
    5.6.3
    5.6.2
    5.6.1
    5.6.0
    5.4.7
    5.4.6
    5.4.5
    5.4.4
    5.4.3
    5.4.2
    5.4.1
    5.4.0
    5.2.10
    5.2.7
    5.2.6
    5.2.4
    5.2.3
    5.2.2
    5.2.1
    5.2.0
    5.0.12
    5.0.11
    5.0.10
    5.0.9
    5.0.8
    5.0.7
    5.0.6
    5.0.5
    5.0.4
    5.0.3
    5.0.2
    4.3.8
    4.3.7
    4.3.6
    4.3.5
    4.3.4
    4.3.3
    4.3.2
    4.3.1
    4.3.0
    4.2.9
    4.2.8
    4.2.7
    4.2.6
    4.2.5
    4.2.4
    4.2.3
    4.2.2
    4.2.1
    4.2.0
    4.1.0
    4.0.3
    4.0.2
    4.0.1
    4.0.0

    Creating Kubernetes connector

    Creating Kubernetes connector

    With FortiManager, you can create a fabric connector for Kubernetes, and then import address names from Kubernetes to automatically create dynamic objects that you can use in policies. When you install the policies to one or more FortiGate units, FortiGate uses the information and Fortinet SDN Connector to communicate with Kubernetes and dynamically populate the objects with IP addresses.

    When you create a fabric connector for Kubernetes, you are specifying how FortiGate can communicate with Kubernetes through Fortinet SDN Connector. As a result, you are configuring communication and authentication information for Fortinet SDN Connector.

    If ADOMs are enabled, you can create multiple fabric connectors per ADOM; however, each fabric connector requires a unique IP address.

    Requirements:

    • FortiManagerwith ADOM version 6.2 or later.

      The method described in this topic for creating fabric connectors requires ADOM version 6.2 or later.

    • FortiGate is managed by FortiManager.
    • The managed FortiGate unit is configured to work with Kubernetes.
    To create a fabric connector object for Kubernetes:
    1. Go to Fabric View > Fabric Connectors.
    2. Click Create New. The Create New Fabric Connector wizard is displayed.
    3. Under Private SDN, select Kubernetes. The Kubernetes screen is displayed.

    4. Configure the following options, and then click OK:

      Name

      Type a name for the fabric connector object.

      Type

      Displays Kubernetes.

      IP

      Type the IP address for the SDN Connector.

      Port

      Specify the port for the Fortinet SDN Connector.

      Select one of the following options:

      • Click Use Default to use the default port.
      • Click Specify and specify the port.

      Secret Token

      Specify a secret token for the Fortinet SDN Connector.

      Update Interval (s)

      Specify the update interval for the Fortinet SDN Connector.

      Select one of the following options:

      • Click Use Default to use the default interval.
      • Click Specify and specify the interval.

      Status

      Toggle On to enable the fabric connector object. Toggle OFF to disable the fabric connector object.
    5. Go to Policy & Objects > Security Fabric > Fabric Connectors. Select the connector and click Import.
    6. The Kubernetes connector is imported. Click Close to close the import dialog.
    7. Create a Policy Package and install it to a FortiGate device. The Kubernetes connector object is synced with the FortiGate device.

    Kubernetes Service must be enabled on the server side for AWS, Azure, OCI and, GCP for Kubernetes to function for the particular cloud platform. Once the service is enabled, Kubernetes can be configured for the particular cloud platform on FortiManager.
    Previous
    Next

    Creating Kubernetes connector

    Creating Kubernetes connector

    With FortiManager, you can create a fabric connector for Kubernetes, and then import address names from Kubernetes to automatically create dynamic objects that you can use in policies. When you install the policies to one or more FortiGate units, FortiGate uses the information and Fortinet SDN Connector to communicate with Kubernetes and dynamically populate the objects with IP addresses.

    When you create a fabric connector for Kubernetes, you are specifying how FortiGate can communicate with Kubernetes through Fortinet SDN Connector. As a result, you are configuring communication and authentication information for Fortinet SDN Connector.

    If ADOMs are enabled, you can create multiple fabric connectors per ADOM; however, each fabric connector requires a unique IP address.

    Requirements:

    • FortiManagerwith ADOM version 6.2 or later.

      The method described in this topic for creating fabric connectors requires ADOM version 6.2 or later.

    • FortiGate is managed by FortiManager.
    • The managed FortiGate unit is configured to work with Kubernetes.
    To create a fabric connector object for Kubernetes:
    1. Go to Fabric View > Fabric Connectors.
    2. Click Create New. The Create New Fabric Connector wizard is displayed.
    3. Under Private SDN, select Kubernetes. The Kubernetes screen is displayed.

    4. Configure the following options, and then click OK:

      Name

      Type a name for the fabric connector object.

      Type

      Displays Kubernetes.

      IP

      Type the IP address for the SDN Connector.

      Port

      Specify the port for the Fortinet SDN Connector.

      Select one of the following options:

      • Click Use Default to use the default port.
      • Click Specify and specify the port.

      Secret Token

      Specify a secret token for the Fortinet SDN Connector.

      Update Interval (s)

      Specify the update interval for the Fortinet SDN Connector.

      Select one of the following options:

      • Click Use Default to use the default interval.
      • Click Specify and specify the interval.

      Status

      Toggle On to enable the fabric connector object. Toggle OFF to disable the fabric connector object.
    5. Go to Policy & Objects > Security Fabric > Fabric Connectors. Select the connector and click Import.
    6. The Kubernetes connector is imported. Click Close to close the import dialog.
    7. Create a Policy Package and install it to a FortiGate device. The Kubernetes connector object is synced with the FortiGate device.

    Kubernetes Service must be enabled on the server side for AWS, Azure, OCI and, GCP for Kubernetes to function for the particular cloud platform. Once the service is enabled, Kubernetes can be configured for the particular cloud platform on FortiManager.
    Previous
    Next