Overview

Team Edition allows the configuration of database connections with specific security settings. This can be done during the initial setup of a new connection or while editing an existing one.

Security restrictions settings

Within the Security section of the connection configuration, the following options are provided:

1. Read-only connection: This setting, when enabled, restricts the connection to read-only operations, ensuring no data can be modified or deleted.

2. By clicking on the Edit permissions, you can access additional security settings:

Setting option	Description
Restrict data edit	Disables the ability to modify data within the database through this connection.
Restrict structure edit	Prohibits alterations to the database structure, such as tables or indices.
Restrict script execute	Prevents script execution, safeguarding against potentially harmful actions.
Restrict data import	Blocks the import of data from external sources into the database.

Tip: For additional settings and restrictions, especially for administrative purposes, refer to documentation on admin preference restrictions.

Overview

There is an Error Log view (main menu Window -> Show View -> Error Log) which contains all errors which occur during the Team Edition runtime.
You can double click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report.
Also, you can open the full log (all error messages) if you need:

DBeaver log files

Standard log file paths

Team Edition writes different log files. Most of them are Eclipse logs. Log files usually reside in the

.

Tip: For detailed guidance on locating your workspace, refer to the workspace location article.

• On Windows, open Explorer and enter the path
  %APPDATA%\DBeaverData\workspace6\.metadata
  .
• On Linux, execute
  cd $XDG_DATA_HOME/DBeaverData/workspace6/.metadata
  .
• On MacOS, navigate to
  ~/Library/DBeaverData/workspace6/.metadata
  in Finder. To view hidden folders, press Cmd+Shift+..

Two standard log files:

• [your_workspace_location]/.metadata/.log
  – contains all warnings and errors occurring during normal operation.
• [your_workspace_location]/.metadata/dbeaver-debug.log
  – includes the same information as
  .log
  plus additional debug details.

Note: The

dbeaver-debug.log

file has a maximum size limit of 10 MB. If the file size exceeds this limit, a new log file is created. Additionally, a new file is generated each time Team Edition is started or restarted.

In special cases, log files can be written in other directories. A special case is an emergency situation when Team Edition cannot start and there is no workspace. Two typical places to find emergency logs:

• <install-path>/configuration

• ${HOME}/.eclipse/org.jkiss.dbeaver.product_<dbeaver-version>

Log files for Team Edition

Log files usually reside in the

.

Tip: For detailed guidance on locating your workspace, refer to the workspace location article.

• On Windows, open Explorer and paste path
  %APPDATA%\DBeaverData\team-workspace\.metadata
  .
• On Linux, just type
  cd $XDG_DATA_HOME/DBeaverData/team-workspace/.metadata

• On macOS, open path

  ~/Library/DBeaverData/team-workspace/.metadata
  in Finder. To view hidden folders, press Cmd+Shift+..

Customizing log files

You can customize the settings for your

file. Follow these steps to configure the log file settings:

1. Navigate to Window -> Preferences -> User Interface -> Error Logs.
2. In the Error Logs settings, you have the following options to customize:

Setting	Description
Enable debug logs	Toggles the recording of debug logs.
Log file location	The directory where dbeaver-debug.log files are stored.
Max log file size (KB)	The maximum size of the log file.
Max backup log files count	The number of backup logs to keep.

Note: These settings take effect after Team Edition is restarted.

Gathering log files for error reporting

When encountering an issue with Team Edition, providing log files is essential for diagnosis. To gather the logs:

1. Navigate to Help -> Collect Diagnostic info.
2. Select the folder to save the collected log information.

Java fatal logs

On the rare occasion that the Team Edition process dies, it does not leave any valuable logs. This is caused by a Java VM crash.
JVM creates a fatal log file for each crash (log gile

). This log usually resides in the same directory where the Team Edition launcher is (e.g. dbeaver.exe).
But in some cases it is a write-protected directory and the log file will be created in other folder.
Instructions on how to find the Java fatal log file: https://docs.oracle.com/javase/9/troubleshoot/fatal-error-log.htm

Overview

Sometimes (due to some bug) Team Edition UI hangs, freezes, or works incorrectly. It is usually impossible to find the reason for such an issue without a thread dump. A thread dump is information about the internal execution state of the Java program.

Team Edition incorporates the

tool for generating thread dumps. To use this pre-installed tool, it is essential to locate its directory in the Team Edition installation and execute it from there.

Important: The

jstack

tool is not included in the tar.gz without Java on the Team Edition download page, and in Downstream packages.

Team Edition includes OpenJDK, which is an open-source version of Java. This means you do not need to purchase a separate Java license to use Team Edition.

Finding jstack

The location of

varies depending on your operating system:

For macOS and Linux

• Find the directory where Team Edition is installed. On macOS, proceed to the

  Contents/Eclipse
  subdirectory. Then, in both macOS and Linux systems, locate the
  jre/bin/jstack
  directory. This is the typical location for
  jstack
  in Team Edition installations.

For Windows

• Find the directory where Team Edition is installed.
• Within this directory, go to
  jre/bin/jstack.exe
  . This is the standard path to find
  jstack
  in Team Edition installations on Windows systems.

Note: If you did not install Java during the Team Edition installation (by unchecking the

Install Java

checkbox),

jstack.exe

will not be present. In this case, you need to install Java separately and locate

jstack.exe

within the Java installation directory.

Generating a thread dump on Windows

To create a thread dump in Team Edition on Windows, follow these steps:

1. Find Team Edition’s Process ID:

   • Open Task Manager by pressing CTRL+SHIFT+ESC.
   • In Windows 8 and later, switch to the “Details” tab.
   • Locate
     DBeaver
     (or
     DBeaver[your version]
     ) in the process list and note its process ID (PID).

   > Tip: For example, if you are using the DBeaver Lite version, you should look for

   DBeaverLite
   .

2. Open Command Prompt:

   • Press Win+R, type
     cmd
     , and press ENTER to open the command prompt.

3. Run the Thread Dump command:

   • Navigate to the
     jre/bin
     directory within the Team Edition installation path.
   • Run the following command, replacing
     PID
     with the actual process ID of Team Edition:
     `
     cmd jstack.exe PID > “%HOMEPATH%\dbeaver-thread-dump.txt”
     `
   • This command executes
     jstack.exe
     , generates a thread dump for the specified PID, and saves the output to
     dbeaver-thread-dump.txt
     in your home directory (e.g.,
     C:\Users\Username
     ). This file contains the thread dump information that can be attached to a GitHub issue for further analysis.

Generating a thread dump on Mac and Linux

To create a thread dump in Team Edition on macOS and Linux systems, you can use the included

tool via the terminal. The following script will generate a thread dump and save it as in your home directory:

/Applications/YOUR-VERSION-OF-DBEAVER.app/Contents/Eclipse/jre/Contents/Home/bin/jstack $(pgrep dbeaver) > ~/dbeaver-thread-dump.txt

Tip: Replace

YOUR-VERSION-OF-DBEAVER.app

with the version of Team Edition you have installed. For example, if you have Team Edition Lite version, the path would be

/Applications/DBeaverLite.app/Contents/Eclipse/jre/Contents/Home/bin/jstack

.

Generating a thread dump without Java

For Linux users

If you are running Team Edition on Linux using the tar.gz version without Java included, you will need to install the Java Development Kit (JDK) to generate a thread dump. Follow these steps:

1. Check for Existing JDK Installation:

   • Open your terminal.
   • Type
     which jstack
     and press Enter.
   • If the JDK is installed, a version number will appear.

2. Install JDK:

   • If JDK is not installed, you need to install it.
   • Use your distribution’s package manager to install JDK. For example, on Ubuntu, you can use
     sudo apt install default-jdk
     .

After successfully installing JDK, proceed with the thread dump script:

jstack $(pgrep dbeaver) > ~/dbeaver-thread-dump.txt

After running this script, you will find the

file in your home directory, containing the necessary thread information for diagnosing issues.

For Windows users

If you are using Team Edition on Windows without Java, consider installing Adoptium OpenJDK.

Alternatively, you can reinstall Team Edition and ensure to check the

checkbox during installation.

After installing Java through either method, you can follow the instructions in the section Generating a Thread Dump on Windows to successfully generate a thread dump.

The default grid view of query results may look unremarkable. Use Team Edition’s Charts feature to transform your

queries into colorized charts. You can visualize data in Bar, Line, or Pie formats.

Create a chart directly in the SQL Editor, Data Editor or Grouping Panel. It’s a quick and simple way to bring your data to life.

Creating Charts In SQL Editor

Visualizing large data sets makes your analysis faster and more precise. Charts let you grasp important details quickly.

To create a chart in the SQL Editor, click the Charts button on the left vertical toolbar of the query results area. Your data instantly transforms into a visual representation.

Creating Charts In Data Editor

Charts are a powerful tool for visualizing structured analytical data, such as those stored in Views.

If you want to create a chart for a table, it requires some preparation. First, sort and apply various filters to the table’s columns to structure the data. These changes directly affect the appearance of the chart, enabling you to customize the visual representation to fit your needs.

To build a chart using the Data Editor, simply press the Charts button located in the left vertical toolbar. A chart based on your structured data will be created.

Note: By default, the data for Y-axis is taken from the first column of the table containing numeric values.

Creating Charts In Grouping Panel

The Charts feature also works with analytical tools like the Grouping Panel. When building a chart for a table that contains grouping results for one or more columns, you can easily switch the source data for the X and Y axes by changing the columns in the Charts Editor.

To create a chart in the Grouping Panel, simply press the Charts button on the left vertical toolbar

Editing Chart Settings

To edit the chart settings, right-click inside the chart area to open the chart’s context menu, and then select the Settings option. The Chart Editor will appear, allowing you to make adjustments.

The following chart settings can be adjusted:

Setting Axis X

• In the Column drop down list of available columns select a column whose data will be used on X-axis of the bar chart. Make sure you choose unique columns for X-axis.

• Define a user-friendly axis name in the Label text field.

Setting Axis Y

• In the Column drop down list of available columns, select a column whose data will be used on Y-axis of the bar chart.
  Note, that only numeric and string columns can be used for Y-axis.
• Define a user-friendly axis name in the Label text field.

• For advanced customization, you can use the Parse value with regex option. Regular expressions (regex) allow you to filter, match, or manipulate the column values according to specific patterns or criteria. This functionality offers precise control over the data displayed on the Y-axis, enabling you to create more refined visual representations. If you’re unfamiliar with regular expressions, the Regular Expressions Tutorial provides comprehensive guidance and examples.

Setting Other Options

You can also set the following chart options:

• Sample count – maximum number of columns used for building a chart.
• Row count – maximum number of rows used for building a chart.
• Chart Type – you can choose how the data will be visualized in Bar, Line, or Pie formats.
• Sample function – an aggregate function where the values of multiple rows are grouped together to form a single summary value displayed on Y-axis.

The following sample functions are supported:

Name	Description
AVG	Average value
SUM	The sum of all values
FIRST	The first value
LAST	The last value
COUNT	Total count of all values
MIN	The minimum value
MAX	The maximum value

Copying to clipboard

You can copy a chart to a clipboard by selecting the Copy to clipboard option in the chart’s context menu.

Exporting Charts

You can export а chart into

format by selecting the Save as… option in the chart’s context menu.

Printing Charts

You can print а chart by selecting the Print… option in the chart’s context menu.

Zooming and Viewing Options

In the chart’s context menu, you will find additional options for interacting with the chart:

• Zoom in: Enlarge the view of the chart.
• Zoom out: Reduce the view of the chart.
• Zoom Reset: Return to the default zoom level.
• View as: Change the visualization format of the chart. A submenu will appear, allowing you to select between Bar, Line, or Pie formats.

The Team Edition formatting functions allow you to set up database locale and change datasource format settings. This feature can be very useful, for example, for database migration.

To change the data format settings use the option Window -> Preferences in main menu.

In the Preferences dialog box go to Editors -> Data Editor -> Data Formats.

Or, in the Database Navigator right-click a connection and select Edit Connection menu option.

In the right area of the opened Data formatting preferences dialog window go to Data editor -> Data Formats and select the Datasource settings check box in the left area to customize the data format settings.

Data Format Profiles

Data format profiles allow you to apply a set of data format preferences to the whole current project by one click.

To create a data format profile press the Manage Profiles button. In the opened dialog window press button New Profile, define the name and press Create.

To delete a data format profile press the Manage Profiles button, then in the opened dialog window select the profile you want to delete and press the button Delete Profile.

Changing Data Formats

The following groups of data format settings can be adjusted:

Locale

To define this setting select a language, country and variant if available.

Native Date and Time Mode

Select Use native date/time format check-box and the data format originally built-in to the datasource will be used.

You can change the format of the following data types:

Data Type Format

The format of the following data types can be customized:

• Date
• Time
• Timestamp

• Numbers

Date

The default value for this data type is yyyy-MM-dd.

Pattern	Description
yyyy or y	Year of era (4 digits)
yy	Year of era (2 last digits)
YYYY	Week year
M	Month in year without leading zeros
MM	Month in year
MMM	Short month name in year
MMMM	Month name in year
D	Day in year
d	Day in month without leading zeros
dd	Day in month
E	Day name in week
G	Era designator
z	General time zone
Z	RFC 822 time zone

Time

The default value for this data type is HH:mm:ss

Pattern	Description
H	Hour in day (0-23) without leading zeros
h	Hour in day in am/pm (1-12) without leading zeros
HH	Hour in day (0-23)
hh	Hour in day in am/pm (1-12)
a	Am/pm marker
m	Minute in hour without leading zeros
mm	Minute in hour
s	Second in minute without leading zeros
ss	Second in minute
S	Millisecond
ffffff	Microseconds

Timestamp

The default value for this data type is yyyy-MM-dd HH:mm:ss

Link on Java date pattern documentation

Numbers

The following parameters can be configured from this type of data:

• Use Grouping – Long numbers can be hard to read if they have too many digits. For example, the factorial of 30 is 33 digits long! Select this check-box to enable Grouping mode, in which digits are displayed in clumps of 3 or 4 (depending on the current radix) separated by commas.

• Maximum integer digits – Defines the maximum number of digits to the left of the decimal point.

• Minimum integer digits – Defines the minimum number of digits to the left of the decimal point.

• Maximum fraction digits – Defines the maximum number of digits to the right of the decimal point.

• Minimum fraction digits – Defines the minimum number of digits to the right of the decimal point.

• Use data type scale for fraction digits – Some numeric columns or parameters may have a predefined scale, that is the maximum number of digits to the right of the decimal point. Select this check-box if you want the predefined precision to be used.

• Rounding mode – Specifies a rounding behavior for numerical operations capable of discarding precision. Each rounding mode indicates how the least significant returned digit of a rounded result is to be calculated. To learn more, please refer to Oracle documentation.

To change the data type format, change the value displayed in the Pattern area,save the changes made by pressing the Apply button and observe the expected result in the Sample field.

Restoring Default Data Formats

To restore the default data format settings, press the Restore Defaults button.

Datasource Settings

Press Datasource settings link to change data format settings for a particular datasource, then adjust the settings in the opened dialog box.

To save changes made press Apply.

You can manage trust store settings in Team Edition to enable secured driver downloads and establish SSL connections. This is achieved by adding or removing certificates from the Custom Truststore. Certificates are integral to establishing secure connections, allowing necessary driver files to be downloaded, and enabling SSL connections to databases. Without the appropriate certificates, you might encounter an error message.

System-specific Features

On Windows operating systems, a system-specific trust store, known as the Windows Truststore, is available. However, this is a read-only trust store.

Note: You cannot import any certificates into this system trust store, it will appear empty. This Windows-specific the option does not display on MacOS or Linux systems.

Viewing certificates is permitted for the Java Truststore, but modifications are impossible.

To modify or manage certificates, Team Edition provides the Custom Truststore.

Managing Certificates

Import Certificates

To import a certificate into the Custom Truststore, follow the steps below:

1) Navigate to Windows -> Preferences -> General -> Security -> Certificates Trust Store and click the Import button.

2) Browse your file system, locate the certificate file (

or ), and select it.

3) Assign an alias to the certificate and click OK.

4) After applying changes to the trust store and clicking Apply and Close, Team Edition prompts a dialog suggesting a restart for the trust store changes to take effect.

Once a certificate is added to the trust store, it enables secure connections and authentication. You can verify the validity of a certificate based on its expiration date.

Viewing and Deleting Certificates

In the Custom Truststore section, select the certificate and click the View button to see detailed information about the certificate. If you need to remove a certificate from the trust store, select the appropriate certificate and click the Delete button.

In some cases, custom JDBC drivers work incorrectly in Team Edition – they show the wrong metadata like table columns, constraints or foreign keys.
It usually happens because the driver is not compliant with the JDBC API specification and Team Edition cannot correctly interpret the metadata provided by the driver.

To understand what is going on inside the driver, you can enable JDBC tracing:

1. Find

   dbeaver.ini
   file.

   Tip: Detailed instructions on finding

   dbeaver.ini

   are available in our article.

2. Add line

   -Ddbeaver.jdbc.trace=true
   in the end of
   dbeaver.ini
   .

3. Restart Team Edition.
4. Connect to your database and browse the metadata in the database navigator/object editors.
5. In Team Edition Workspace go to
   .metadata
   folder.
6. File
   jdbc-api-trace.log
   contains all JDBC API invocations and all queries with results.

Analyzing contents of

you can understand what is wrong with the metadata. Attach the piece of the trace file in the GitHub ticket if you think that something is wrong on Team Edition’s side.

WARNING: disable JDBC tracing in your regular work. Enable it only for debugging. The trace generation decreases application performance and may produce huge log files.

Overview

Team Edition includes support for Kerberos authentication, enabling secure connections to your databases.

Kerberos authentication is a secure method for verifying user identities over non-secure networks. It is widely used in various environments, especially in database management systems, to ensure that communication between the client and server remains encrypted and authenticated.

This guide is designed to help you configure Kerberos authentication on the client machine, where Team Edition is installed. It assumes that the Kerberos Key Distribution Center (KDC) and the necessary server configurations have already been completed.

Supported databases

• AlloyDB
• Cockroach
• EnterpriseDB (EDB)
• Fujitsu
• Greenplum
• HANA
• MariaDB
• MySQL
• Oracle
• PostgreSQL
• PrestoDB
• PrestoSQL
• Redshift
• Teradata
• TimescaleDB
• Trino
• Yellowbrick

• YugabyteDB

Settings

The table below lists the basic settings required for Kerberos authentication in Team Edition. These settings are essential for establishing a secure connection to your database using Kerberos, providing user identification, authentication, and access control.

Setting	Description
Username	Specifies the name of the user or role within the database. This is the identity under which you will connect to your database.
Kerberos user	A unique identity in the Kerberos system to which Kerberos can assign tickets, enabling access to services that are Kerberos-aware.
Realm	The domain over which a Kerberos authentication server can authenticate users, hosts, or services. It’s often the uppercase version of the DNS domain name it oversees.
KDC Server	The hostname of your Kerberos Key Distribution Center (KDC), which is a service that provides session tickets and keys within an Active Directory domain.
Password	The password associated with your Kerberos user. This method involves directly entering your password. It’s a simple, manual process suitable for environments where automated authentication methods are not preferred or available.

Below are additional Kerberos authentication settings for advanced configuration:

Extra configuration	Description
Use kinit	When selected, it indicates the use of the kinit tool on your machine, which obtains and caches an initial ticket-granting ticket. Generally, you only need to provide your Kerberos username when this option is selected. Selecting this option makes the Password field inactive because authentication is managed through the ticket obtained by kinit .
Use keytab	A checkbox option for those who prefer to use a keytab file instead of manually entering a password. Selecting this option also makes the Password field inactive because the keytab file contains encrypted keys that the Kerberos system uses for authentication.
Custom krb5.conf	Allows you to specify the path to your local Kerberos configuration file. This file contains settings that define the Kerberos realms, KDCs, and other parameters for your environment.
Debug Kerberos Connection	A checkbox that, when selected, enables the logging of detailed Kerberos connection information in your log files.

Note: Some settings may be stored in a session cache. If you have updated the settings and still encounter connection issues, restarting Team Edition might be necessary to apply the changes effectively.

Extra configuration

The Extra configuration section within Team Edition’s connection settings offers advanced options for customizing the Kerberos. This section allows users to specify detailed settings, such as the use of a keytab file,

commands, or a custom / file.

Using the kinit

The

command is a utility Kerberos provides to obtain and cache an initial ticket-granting ticket (TGT).

In the context of using Team Edition, the

command streamlines the authentication process by obtaining and caching an initial ticket-granting ticket (TGT). This mechanism enables users to authenticate against Kerberos-enabled services, reducing the need for continuous password inputs during the session.

To configure Kerberos authentication using

command, follow these steps:

1. Make sure you have a valid Kerberos ticket-granting ticket (TGT), which can be obtained using the
   kinit
   command. For a detailed guide, refer to the official documentation on
   kinit
   command.
2. Specify the path to your
   kinit
   tool in the Extra Configuration section in the Use kinit field.
3. Try connecting to your database. With these settings, Team Edition will use the
   kinit
   command for authentication.

Using the keytab file

A keytab is a file containing pairs of Kerberos principals and encrypted keys derived from the Kerberos password. It enables authentication to various remote systems using Kerberos without entering a password.

In the context of using Team Edition, the keytab file simplifies the authentication process by requiring the user to provide all necessary credentials except the password.

To configure Kerberos authentication using a keytab file, follow these steps:

1. Utilize the
   ktutil
   command-line utility to generate a keytab file. This involves adding entries for your principals along with their encrypted keys. For comprehensive instructions on creating a keytab file, consult the official documentation on creating a Kerberos keytab file.
2. Specify the path to your keytab file in the Extra Configuration section in the Use keytab field.
3. Attempt to connect to your database. Team Edition will utilize the specified keytab file for authentication.

Windows specifics

On Linux and macOS,

and keytab files are supported natively. However, Windows does not support these functionalities natively. To enable these features, Windows users need to install additional software.

A key tool for Windows users is MIT Kerberos for Windows. It allows the use of

and provides utilities for managing keytab files, bridging the gap between Windows and Kerberos authentication standards.

Local Kerberos configuration file

If you have a custom Kerberos configuration file (

/ ), input the complete file path in the Custom krb5.conf field.

The configuration file includes necessary configuration details such as KDCs and admin server locations for Kerberos realms, default values for the current Realm, and hostname to Kerberos realm mappings. If a custom configuration file path is provided, it is not necessary to fill in the standard authentication fields, as the configuration file contains all the required information.

Additional settings

When configuring PrestoSQL and Trino connections, especially in environments that utilize Kerberos authentication and SSL, certain additional settings might be necessary for connection:

Setting	Description
Service name	Add the Kerberos service name of the remote coordinator.
Use SSL from JKS	Check this setting and manually add the file path to your .jks file if you need an SSL certificate from a JKS file. This is useful when the server’s SSL certificate is not automatically trusted. If your JKS file is password-protected, add the password to the SSL JKS Password field to allow database to access the keystone.
SSL JKS Password	For additional security, the JKS file is password-protected. Add the password to the “SSL JKS” field to allow database to access the keystone.

Troubleshooting

Oracle JDBC driver and Kerberos authentication

When configuring Kerberos authentication for Oracle databases, it is important to be aware of compatibility issues with certain JDBC driver versions. Specifically, Oracle JDBC driver version 21 has been known to cause issues with Kerberos authentication, often not working with older configurations.

To ensure Kerberos authentication functions properly with Oracle databases, it is recommended to use an older version of the Oracle JDBC driver. Versions 12.x or 19.x are known to be compatible and should be used for Kerberos authentication. By selecting one of these older driver versions, you can avoid the authentication problems introduced in version 21.

In some scenarios, you may need to interact with databases that are part of a Kubernetes cluster. Team Edition offers a way to configure Kubernetes settings to facilitate this. Before proceeding, ensure that you meet the following prerequisites:

You must have the kubectl tool installed on your local machine.

You need a Kubernetes configuration file. Use the local one or consult your administrator for access.

Setting up Kubernetes

To set up a tunnel to a Kubernetes cluster in Team Edition, you need to configure the following settings:

1) First, you need to add a Network Handler for Kubernetes. To do this, click on the Network configurations… button and select Kubernetes.

2) After making your selection, a new tab will appear in the menu at the top, where you can proceed to configure the various settings.

Here you need to fill out the following fields:

Field	Description
Configuration	Specify the path to your Kubernetes configuration file.
Context	Manually select a kube-context if your configuration offers multiple contexts for different clusters. The default setting is default .
Namespace	The default value is default , but this may differ in managed Kubernetes environments. Obtain the correct namespace from your kubectl config.
Resource	By clicking the Find Resource button next to the field, a list of available services to connect to will open. From this list, you can select the service you wish to connect to.
Port	Configure Kubernetes port forwarding by using kubectl .

Tip: When clicking the dropdown menus in Context and Namespace, you can select settings directly from your

config.

Kubectl settings

The Kubernetes Command-Line Tool,

, is essential for interacting with Kubernetes clusters and is integral to the functioning of Team Edition’s Kubernetes features. Learn more in the official Kubernetes documentation.

To configure

settings, you have two options:

1) Click on Configuration button on the Kubernetes connection settings page to access the

settings.

2) Alternatively, navigate to Window -> Preferences -> Connections -> Command Line Tools -> Kubernetes to specify the path to your

executable.

Testing port forwarding

The Test port forwarding button utilizes the

feature to enable secure access to applications running inside Pods from your local machine. This provides a secure way to interact with the application without exposing it to the outside world. Learn more in the official Kubernetes documentation.

To test port forwarding:

1) Fill out the necessary Kubernetes settings as described in the previous section.

2) Click on the Test port forwarding button to initiate the port forwarding process.

If the test is successful, this confirms that you can securely access the targeted Kubernetes resource from your local machine using the configured port settings.