Container limitations and Licensing Requirements
Hi, I have three questions about containers:
1) Can you run fully on containers once the migration is complete, or do you need to keep around the original “base server” that is not a container?
2) Are there any limitations to the containers compared to a full server?
3) Does creating additional Kubernetes instances of the same environment does not require additional licensing costs?
Comments
-
1 -- Yes, you can fully run a container without the original server.
2 -- Here are a few:
- You cannot use localhost/127.0.0.1
- PowerShell/Python scripts using Windows syntax paths or utilities will fail, since containers run Linux
- Windows Integrated Security and Service accounts as well as SQL authentication aren't supported on containers for the same reason as PowerShell/python limitations
3 -- Each server will need its own license unless they point to the same database and are in a cluster.
Howdy, Stranger!
Categories
- 4.2K All Categories
- 66 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 490 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions