# Page Not Found

The URL `self-managed-deployment/upgrade-overview/upgrade-iehc-2024.2-lts-to-2024.3` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Upgrading (IEHC)](https://documentation.immuta.com/2024.3/self-managed-deployment/upgrade-overview/upgrade-immuta.md)
- [Upgrading (IHC)](https://documentation.immuta.com/2024.3/self-managed-deployment/upgrade-overview/upgrade-with-ihc.md)
- [Migrating to the New Helm Chart](https://documentation.immuta.com/2024.3/self-managed-deployment/upgrade-overview/migrate-to-iehc.md)
- [Upgrade](https://documentation.immuta.com/2024.3/self-managed-deployment/upgrade-overview.md)
- [Ingress Configuration](https://documentation.immuta.com/2024.3/self-managed-deployment/configure/ingress-configuration.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://documentation.immuta.com/2024.3/self-managed-deployment/upgrade-overview/upgrade-immuta.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://documentation.immuta.com/2024.3/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://documentation.immuta.com/2024.3/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/2024.3/self-managed-deployment/upgrade-overview/upgrade-immuta.md`).

You may also use `Accept: text/markdown` header for content negotiation.