Skip to main content
Note: This documentation has been checked and approved for Kubernetes 1.34.0 and Flannel 0.27.4 versions. Ports may vary in different Kubernetes and Flannel versions.
Apinizer does not recommend installing on a single server for production environments. Consider such an installation configuration only for PoC environments.

Before Starting Installation

Before starting the Apinizer installation, you need to prepare and make decisions on the following topics:

1. Deployment Model Selection

Apinizer offers three basic deployment models suitable for different requirements:

2. Pre-Installation Decisions

You need to make decisions on the following topics before installation:

3. Access and Port Requirements

You should check the internet access and port requirements needed for installation. For detailed information, see the Access and Port Requirements for Installation page.

4. Installation Directory Guide

You can use the pages under the /en/setup directory to perform installation operations. What each page is used for is explained below.

Pre-Installation Decisions

For detailed information, see the Pre-Installation Decisions page.

Access and Port Requirements

For detailed information, see the Access and Port Requirements for Installation page.

Installation Directory Guide

All documentation related to Apinizer installation is located under the /en/setup directory.

Installation Group

Infrastructure Components Group

Kubernetes

Elasticsearch

MongoDB

Cloud

Helm

Offline

Important Notes

  • Making all decisions before installation and completing necessary preparations will speed up the installation process
  • Deployment model selection determines installation topology and resource requirements
  • It is important to check port and access requirements before installation
  • If you will do offline installation, you should prepare all necessary packages in advance
  • Installing on a single server is not recommended for production environments
  • Do not use test/PoC installations for load testing purposes
  • Always take backups before critical operations
  • Port changes should be made carefully if they will be made

Next Steps